Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7282107c6c972bd71624130c081ce26fbfd1786bdf6713de80140cf45042d9de

Tx prefix hash: b98b5e5d6626efc280957bc954c64748b7cabf56d8596cc785153bd688156098
Tx public key: bb1a74e9b3d80f9e5c32acfba3bbd9b26f057c8170fd5a1b2b05a88cfba53800
Timestamp: 1721587242 Timestamp [UCT]: 2024-07-21 18:40:42 Age [y:d:h:m:s]: 00:218:11:53:01
Block: 1070699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156048 RingCT/type: yes/0
Extra: 01bb1a74e9b3d80f9e5c32acfba3bbd9b26f057c8170fd5a1b2b05a88cfba5380002110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 517821f0c2ff0e18bc79fa897be18590a71596f04132709f4bc3be205ac82eef 0.600000000000 1542644 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": 1070709, "vin": [ { "gen": { "height": 1070699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "517821f0c2ff0e18bc79fa897be18590a71596f04132709f4bc3be205ac82eef" } } ], "extra": [ 1, 187, 26, 116, 233, 179, 216, 15, 158, 92, 50, 172, 251, 163, 187, 217, 178, 111, 5, 124, 129, 112, 253, 90, 27, 43, 5, 168, 140, 251, 165, 56, 0, 2, 17, 0, 0, 0, 9, 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