Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d1fea28dbd3318503c833557ad7e12f363fdff6cc5d04a31bede2894cd35c15

Tx prefix hash: 907ddd1a09e6c7c1ae09d0064dc7049b358ef9e593762c1c545219d68dd77623
Tx public key: e08d85babe9e650bc4a1c1d027a500de0be350e56962ce32dcc067a3d718155a
Timestamp: 1725213343 Timestamp [UCT]: 2024-09-01 17:55:43 Age [y:d:h:m:s]: 00:074:14:37:24
Block: 1100782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53343 RingCT/type: yes/0
Extra: 01e08d85babe9e650bc4a1c1d027a500de0be350e56962ce32dcc067a3d718155a02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3f06c6e3b6f13e4161b07c111e8ef55d55e15989cd1ae255af2c4eb015cbbc2 0.600000000000 1576763 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": 1100792, "vin": [ { "gen": { "height": 1100782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3f06c6e3b6f13e4161b07c111e8ef55d55e15989cd1ae255af2c4eb015cbbc2" } } ], "extra": [ 1, 224, 141, 133, 186, 190, 158, 101, 11, 196, 161, 193, 208, 39, 165, 0, 222, 11, 227, 80, 229, 105, 98, 206, 50, 220, 192, 103, 163, 215, 24, 21, 90, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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