Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a291c35658a8c6e811c1798d648f8c43f7dc319ad5da126dd3172208c66ffad

Tx prefix hash: 8a9c2f3ebaa3c7e8969ed10ce32ddc93497a114e7c38c46dad99b560781c6818
Tx public key: b90db0cc482ac9b6a650fc0913a5b0ea43b58230f3a201dd8f542c840487b163
Timestamp: 1734829867 Timestamp [UCT]: 2024-12-22 01:11:07 Age [y:d:h:m:s]: 00:000:12:31:48
Block: 1180412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372 RingCT/type: yes/0
Extra: 01b90db0cc482ac9b6a650fc0913a5b0ea43b58230f3a201dd8f542c840487b1630211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed7fdb598f393f5b87b68f800b623db4f032589fab637c5e6a8c3f792293b2a2 0.600000000000 1666823 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": 1180422, "vin": [ { "gen": { "height": 1180412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed7fdb598f393f5b87b68f800b623db4f032589fab637c5e6a8c3f792293b2a2" } } ], "extra": [ 1, 185, 13, 176, 204, 72, 42, 201, 182, 166, 80, 252, 9, 19, 165, 176, 234, 67, 181, 130, 48, 243, 162, 1, 221, 143, 84, 44, 132, 4, 135, 177, 99, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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