Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1979bfd4e5ad675b0be424b62cc41feb3bce1d7ab0150ecd95f43fc8a2f97e3d

Tx prefix hash: 7b785760337b434092087245f9f8c7760efbded739f8933295544331bade8e82
Tx public key: 00c9a8a9e7e5bbb1bdf80e182d0ad247df12750d915fdc4b050c235bda40e339
Timestamp: 1681200934 Timestamp [UCT]: 2023-04-11 08:15:34 Age [y:d:h:m:s]: 02:044:08:41:43
Block: 736129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 553905 RingCT/type: yes/0
Extra: 0100c9a8a9e7e5bbb1bdf80e182d0ad247df12750d915fdc4b050c235bda40e33902110000000575e3f0e9000000000000000000

1 output(s) for total of 2.233054203000 dcy

stealth address amount amount idx
00: eaa85118200b1d5eb84341240af12a736fed3a7314d4fbfcea9913e28ecf39b3 2.233054203000 1182528 of 0

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": 736139, "vin": [ { "gen": { "height": 736129 } } ], "vout": [ { "amount": 2233054203, "target": { "key": "eaa85118200b1d5eb84341240af12a736fed3a7314d4fbfcea9913e28ecf39b3" } } ], "extra": [ 1, 0, 201, 168, 169, 231, 229, 187, 177, 189, 248, 14, 24, 45, 10, 210, 71, 223, 18, 117, 13, 145, 95, 220, 75, 5, 12, 35, 91, 218, 64, 227, 57, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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