Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6a6d9f7ff4d4c82f34661efbcc1ce34c6a5e59ea84e28b67684fed577e7905f

Tx prefix hash: 996d790c3de199c3da1383de8573c2ded8c0c546262ab03121581c6841117dca
Tx public key: ee35f8bc728e2a811f3d0f8da4dd5be30c8a60906a126cc5ff248be0c58687c2
Timestamp: 1702406889 Timestamp [UCT]: 2023-12-12 18:48:09 Age [y:d:h:m:s]: 01:133:20:02:37
Block: 911715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356788 RingCT/type: yes/0
Extra: 01ee35f8bc728e2a811f3d0f8da4dd5be30c8a60906a126cc5ff248be0c58687c202110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a8f67fb5e8e7b60c3aa1dd721e3e7aa6840b6d001388e5f63b90f59d33c2e2c 0.600000000000 1368931 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": 911725, "vin": [ { "gen": { "height": 911715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a8f67fb5e8e7b60c3aa1dd721e3e7aa6840b6d001388e5f63b90f59d33c2e2c" } } ], "extra": [ 1, 238, 53, 248, 188, 114, 142, 42, 129, 31, 61, 15, 141, 164, 221, 91, 227, 12, 138, 96, 144, 106, 18, 108, 197, 255, 36, 139, 224, 197, 134, 135, 194, 2, 17, 0, 0, 0, 2, 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