Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d94f03a2dbd5f5ebd566023deb41553a514ebeb5468b90b160e69f68cd441283

Tx prefix hash: bc41ce5c97f6b09a6ec36b5f1acfc9f4b26035535f8650ff39ffb2fba58c1d19
Tx public key: 8e7262e0d6bca77097ae63e43248155ee338c9544884e2bac01e4a39a057c9c9
Timestamp: 1725209808 Timestamp [UCT]: 2024-09-01 16:56:48 Age [y:d:h:m:s]: 00:214:08:46:11
Block: 1100748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153046 RingCT/type: yes/0
Extra: 018e7262e0d6bca77097ae63e43248155ee338c9544884e2bac01e4a39a057c9c9021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fa4925403a8b0da794819a2d8aba26e6bee44c0d49a96c6b33f2ab7556a728b 0.600000000000 1576729 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": 1100758, "vin": [ { "gen": { "height": 1100748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fa4925403a8b0da794819a2d8aba26e6bee44c0d49a96c6b33f2ab7556a728b" } } ], "extra": [ 1, 142, 114, 98, 224, 214, 188, 167, 112, 151, 174, 99, 228, 50, 72, 21, 94, 227, 56, 201, 84, 72, 132, 226, 186, 192, 30, 74, 57, 160, 87, 201, 201, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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