Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af3ed469e6bab79d6cab829e8b2da369fb322291c5f2a0eef5b454d3a15fc5ce

Tx prefix hash: c509ceb4a1cff474ba3deadf79739cb55c875ded25948e919f645f4bcbb284aa
Tx public key: b5e998aa09dec45c65ee82bf4b7fd4ac3225bf2433251b5e415c222980d4a533
Timestamp: 1736115656 Timestamp [UCT]: 2025-01-05 22:20:56 Age [y:d:h:m:s]: 00:313:19:18:42
Block: 1191031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221777 RingCT/type: yes/0
Extra: 01b5e998aa09dec45c65ee82bf4b7fd4ac3225bf2433251b5e415c222980d4a53302110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7a6640fe3e04154be7d3c6a920e45510d80bfd66a4053f37fba49f887daa197 0.600000000000 1677554 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": 1191041, "vin": [ { "gen": { "height": 1191031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7a6640fe3e04154be7d3c6a920e45510d80bfd66a4053f37fba49f887daa197" } } ], "extra": [ 1, 181, 233, 152, 170, 9, 222, 196, 92, 101, 238, 130, 191, 75, 127, 212, 172, 50, 37, 191, 36, 51, 37, 27, 94, 65, 92, 34, 41, 128, 212, 165, 51, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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