Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f1c12a75820e9c36834692a8cba56017261cc2dd5e07f23bbee11490419a6b5

Tx prefix hash: 1196b9f14a4d3c4e0fea77f8d764ea2a37f480e26d0abaf3d3a61aefab8f4b40
Tx public key: 6df99c13a05ece20a986dddff36c73c88035edbc60c705bb320eaa60a1d22717
Timestamp: 1729180233 Timestamp [UCT]: 2024-10-17 15:50:33 Age [y:d:h:m:s]: 00:000:22:36:01
Block: 1133663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 678 RingCT/type: yes/0
Extra: 016df99c13a05ece20a986dddff36c73c88035edbc60c705bb320eaa60a1d2271702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4846ec0d949be4c0a00dc9a4716f1b8ae5e90a572925589aa46e3405a48faeee 0.600000000000 1616844 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": 1133673, "vin": [ { "gen": { "height": 1133663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4846ec0d949be4c0a00dc9a4716f1b8ae5e90a572925589aa46e3405a48faeee" } } ], "extra": [ 1, 109, 249, 156, 19, 160, 94, 206, 32, 169, 134, 221, 223, 243, 108, 115, 200, 128, 53, 237, 188, 96, 199, 5, 187, 50, 14, 170, 96, 161, 210, 39, 23, 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