Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a41750168b6ac4c4e3ca5fab52fc7399d159f5740ba3896d5567ca4e8330658c

Tx prefix hash: 951831c8b62ab9e6288392c1bc2818964a228c1fef5bc6bab9019cab9bb568b3
Tx public key: 61393f7ff69ac6121f9bb7e824ba05918d7030be8d0badbfae4d5f877f5dcadb
Timestamp: 1708913878 Timestamp [UCT]: 2024-02-26 02:17:58 Age [y:d:h:m:s]: 01:031:01:03:52
Block: 965653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283184 RingCT/type: yes/0
Extra: 0161393f7ff69ac6121f9bb7e824ba05918d7030be8d0badbfae4d5f877f5dcadb02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5a53a81124c1c8a6cf0e8274051a80f3c3e537665287a2d3154d870a3b77d9e 0.600000000000 1425408 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 965663, "vin": [ { "gen": { "height": 965653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5a53a81124c1c8a6cf0e8274051a80f3c3e537665287a2d3154d870a3b77d9e" } } ], "extra": [ 1, 97, 57, 63, 127, 246, 154, 198, 18, 31, 155, 183, 232, 36, 186, 5, 145, 141, 112, 48, 190, 141, 11, 173, 191, 174, 77, 95, 135, 127, 93, 202, 219, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8