Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc603cc224d4cfd992fd395245ed118c730657061782ae90bb2b0c2be90b581a

Tx prefix hash: 2ce658f6bcfb3a0a358adca204d8eecb1da889ed688dd05b35a3c62eb7115c92
Tx public key: cc65dd529d56b5899a8e2abcac85031be735962a14df5e91a4e623be695a357a
Timestamp: 1704037743 Timestamp [UCT]: 2023-12-31 15:49:03 Age [y:d:h:m:s]: 01:058:14:33:02
Block: 925210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302964 RingCT/type: yes/0
Extra: 01cc65dd529d56b5899a8e2abcac85031be735962a14df5e91a4e623be695a357a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24d64cc41bdc849e38cb041bbfb1f698308d4ca56eae9d69d2ced8d923374fec 0.600000000000 1382970 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": 925220, "vin": [ { "gen": { "height": 925210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24d64cc41bdc849e38cb041bbfb1f698308d4ca56eae9d69d2ced8d923374fec" } } ], "extra": [ 1, 204, 101, 221, 82, 157, 86, 181, 137, 154, 142, 42, 188, 172, 133, 3, 27, 231, 53, 150, 42, 20, 223, 94, 145, 164, 230, 35, 190, 105, 90, 53, 122, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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