Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ed284908745298b4b21dc386d5c8805b655dde536fba424fb930aecc64489a1

Tx prefix hash: 3876c52b2a7d5fccb215ac792c40ffd13ac887a3f8de820e030d443b6adde382
Tx public key: 881cc06a7bc5bed8f64ef6f3f66c7b7babe3f7ebad34afe9111ff60d74ecffc6
Timestamp: 1747438269 Timestamp [UCT]: 2025-05-16 23:31:09 Age [y:d:h:m:s]: 00:182:23:52:20
Block: 1284492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128495 RingCT/type: yes/0
Extra: 01881cc06a7bc5bed8f64ef6f3f66c7b7babe3f7ebad34afe9111ff60d74ecffc60211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ced7a68ae5d63285b2c87fdc35ffaf07bb49ad50f93bc15d7bdf42de3a5484e7 0.600000000000 1771947 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": 1284502, "vin": [ { "gen": { "height": 1284492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ced7a68ae5d63285b2c87fdc35ffaf07bb49ad50f93bc15d7bdf42de3a5484e7" } } ], "extra": [ 1, 136, 28, 192, 106, 123, 197, 190, 216, 246, 78, 246, 243, 246, 108, 123, 123, 171, 227, 247, 235, 173, 52, 175, 233, 17, 31, 246, 13, 116, 236, 255, 198, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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