Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2bd98db849377d5bdfd4968ce7ce442366470faa48a2b15e9d3807a0fe35673

Tx prefix hash: 7f6c323be0f5e8df0f8f6e5a803f20b1a85b273cdbb1bdad5493884b025aa3de
Tx public key: a2ccf427697cb915190d6f4760473015bb8dec0b20ede07274d9d4e36e21417f
Timestamp: 1712539296 Timestamp [UCT]: 2024-04-08 01:21:36 Age [y:d:h:m:s]: 01:044:08:10:06
Block: 995675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292703 RingCT/type: yes/0
Extra: 01a2ccf427697cb915190d6f4760473015bb8dec0b20ede07274d9d4e36e21417f02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d13dbeabb8da2622ce844afcefaf56fc6666ea52f3e2e70a64a2953279358c2 0.600000000000 1456089 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": 995685, "vin": [ { "gen": { "height": 995675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d13dbeabb8da2622ce844afcefaf56fc6666ea52f3e2e70a64a2953279358c2" } } ], "extra": [ 1, 162, 204, 244, 39, 105, 124, 185, 21, 25, 13, 111, 71, 96, 71, 48, 21, 187, 141, 236, 11, 32, 237, 224, 114, 116, 217, 212, 227, 110, 33, 65, 127, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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