Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d512e6549d83e48c7f1d4422c11a1240286f8435ccf2338e541f6685ebaa3fd

Tx prefix hash: 5d1c6dcff6e2ebe4ec15e5ad8340d4ce4237e92f6e01b6a91d584fe448637eac
Tx public key: 42054a02653fb0619c356f7c99e5a8ac487d7dd696825aba1792be553306447c
Timestamp: 1700148818 Timestamp [UCT]: 2023-11-16 15:33:38 Age [y:d:h:m:s]: 01:327:05:23:34
Block: 892984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492708 RingCT/type: yes/0
Extra: 0142054a02653fb0619c356f7c99e5a8ac487d7dd696825aba1792be553306447c021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.674797254000 dcy

stealth address amount amount idx
00: cc6710647494a73c19f9bebca76dfcfe95d0ae2537822b393eaeb3ee0b7a2fcb 0.674797254000 1349147 of 0

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": 892994, "vin": [ { "gen": { "height": 892984 } } ], "vout": [ { "amount": 674797254, "target": { "key": "cc6710647494a73c19f9bebca76dfcfe95d0ae2537822b393eaeb3ee0b7a2fcb" } } ], "extra": [ 1, 66, 5, 74, 2, 101, 63, 176, 97, 156, 53, 111, 124, 153, 229, 168, 172, 72, 125, 125, 214, 150, 130, 90, 186, 23, 146, 190, 85, 51, 6, 68, 124, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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