Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb62d586e41fe35d80b7affc03deabdeaf5d41f74cf3d3a15c3f9231aaa704d5

Tx prefix hash: 8b4d965d25a131756b9e8c78aea203ea539cd6fef3821c10efeea8da4581c234
Tx public key: 8c13c3d95543edc14b03ac67b09486ae338ffe4fea5d01f7e72042f130aa1d56
Timestamp: 1722156633 Timestamp [UCT]: 2024-07-28 08:50:33 Age [y:d:h:m:s]: 00:258:10:22:30
Block: 1075431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184618 RingCT/type: yes/0
Extra: 018c13c3d95543edc14b03ac67b09486ae338ffe4fea5d01f7e72042f130aa1d56021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d48f7dcedfe7450ea64e7331dd10a630555a009e344f921404f7dd243837f65e 0.600000000000 1547956 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": 1075441, "vin": [ { "gen": { "height": 1075431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d48f7dcedfe7450ea64e7331dd10a630555a009e344f921404f7dd243837f65e" } } ], "extra": [ 1, 140, 19, 195, 217, 85, 67, 237, 193, 75, 3, 172, 103, 176, 148, 134, 174, 51, 143, 254, 79, 234, 93, 1, 247, 231, 32, 66, 241, 48, 170, 29, 86, 2, 17, 0, 0, 0, 4, 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