Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d0a4a83c783ad9a4f8f4de9516602a2e711452ac182cebf018655677fbb403a

Tx prefix hash: 833d826400e5bf9de2293df3857427e5b51a06ee31e43730afc2a3d691ac64f8
Tx public key: 8125b0d5a19f959c40482dd283527313a1ff19ae19d0c553d772f0adb52ee3eb
Timestamp: 1721367397 Timestamp [UCT]: 2024-07-19 05:36:37 Age [y:d:h:m:s]: 00:282:03:11:39
Block: 1068906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201562 RingCT/type: yes/0
Extra: 018125b0d5a19f959c40482dd283527313a1ff19ae19d0c553d772f0adb52ee3eb02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eeae575ebc838c7d1878d8ca2527ee62b555bbae646c8373043a2b7875aa6588 0.600000000000 1540121 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": 1068916, "vin": [ { "gen": { "height": 1068906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eeae575ebc838c7d1878d8ca2527ee62b555bbae646c8373043a2b7875aa6588" } } ], "extra": [ 1, 129, 37, 176, 213, 161, 159, 149, 156, 64, 72, 45, 210, 131, 82, 115, 19, 161, 255, 25, 174, 25, 208, 197, 83, 215, 114, 240, 173, 181, 46, 227, 235, 2, 17, 0, 0, 0, 1, 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