Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a72f7d29c98ba403450ca20d76507202a44aaf687c9d2ab696e041f25b5b4be

Tx prefix hash: 05e976bb88abc5c7b7b79fee2661d27ae73fc37a747b863391f0fc0851006d13
Tx public key: db2ae933d6d7195715883c7a78f7028dabfb4102d2a52a7dc067ec3a81bafbdf
Timestamp: 1731039758 Timestamp [UCT]: 2024-11-08 04:22:38 Age [y:d:h:m:s]: 00:059:06:13:51
Block: 1149000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42403 RingCT/type: yes/0
Extra: 01db2ae933d6d7195715883c7a78f7028dabfb4102d2a52a7dc067ec3a81bafbdf0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33a5920aab6c8004f005696fe42620d9a1d01f301f1c314b3047c7a4448275ea 0.600000000000 1633979 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": 1149010, "vin": [ { "gen": { "height": 1149000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33a5920aab6c8004f005696fe42620d9a1d01f301f1c314b3047c7a4448275ea" } } ], "extra": [ 1, 219, 42, 233, 51, 214, 215, 25, 87, 21, 136, 60, 122, 120, 247, 2, 141, 171, 251, 65, 2, 210, 165, 42, 125, 192, 103, 236, 58, 129, 186, 251, 223, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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