Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ffabff591cc4bf1b92f6e7ea5bd18745408c0201d9739e62632a573652047d0

Tx prefix hash: c14a2d85aa314e7129ac10c99cabe0a210737854c4156500e4904237a397ee07
Tx public key: b99dd0e8ccbe2a12df10b2f5f3d4ba16b1d4d4d4b1f3c9e65f5de29143e4be11
Timestamp: 1728318974 Timestamp [UCT]: 2024-10-07 16:36:14 Age [y:d:h:m:s]: 01:032:23:57:43
Block: 1126522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281970 RingCT/type: yes/0
Extra: 01b99dd0e8ccbe2a12df10b2f5f3d4ba16b1d4d4d4b1f3c9e65f5de29143e4be11021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d090dd3d0830c2fc1b02ca4f46fef6407d167b0e6f9eb9266ba4e9dbf570e42 0.600000000000 1609317 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": 1126532, "vin": [ { "gen": { "height": 1126522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d090dd3d0830c2fc1b02ca4f46fef6407d167b0e6f9eb9266ba4e9dbf570e42" } } ], "extra": [ 1, 185, 157, 208, 232, 204, 190, 42, 18, 223, 16, 178, 245, 243, 212, 186, 22, 177, 212, 212, 212, 177, 243, 201, 230, 95, 93, 226, 145, 67, 228, 190, 17, 2, 17, 0, 0, 0, 1, 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