Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db9022f8575ceead288fd1427c3c38297a76e501afd3af7ba5af23dc99305cfb

Tx prefix hash: 1c561cc6707b807a47e9d540b8ec2a554b7ae23ff6ca4756443c72e10277a21d
Tx public key: 87ea0aafd6efd97e4af9a457c2c0223fd944f660f504453f6e11010aca85ea47
Timestamp: 1577082580 Timestamp [UCT]: 2019-12-23 06:29:40 Age [y:d:h:m:s]: 04:319:13:19:26
Block: 29873 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117431 RingCT/type: yes/0
Extra: 0187ea0aafd6efd97e4af9a457c2c0223fd944f660f504453f6e11010aca85ea470211000000178a2ee0d9000000000000000000

1 output(s) for total of 488.673977139000 dcy

stealth address amount amount idx
00: 8f8b40e42378915c2a729f3712bcf18cbadbb1a56daecf64fb7c8dc1ce901f0c 488.673977139000 49271 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": 29883, "vin": [ { "gen": { "height": 29873 } } ], "vout": [ { "amount": 488673977139, "target": { "key": "8f8b40e42378915c2a729f3712bcf18cbadbb1a56daecf64fb7c8dc1ce901f0c" } } ], "extra": [ 1, 135, 234, 10, 175, 214, 239, 217, 126, 74, 249, 164, 87, 194, 192, 34, 63, 217, 68, 246, 96, 245, 4, 69, 63, 110, 17, 1, 10, 202, 133, 234, 71, 2, 17, 0, 0, 0, 23, 138, 46, 224, 217, 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