Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6cab00275c8b2abbcdd42b6746f50f3864c21dc0629f1d251d74a23016ed079

Tx prefix hash: cc1884157d0ddccaa4ddb50a90a4c1958e0b9a45b0c1c9c02875ee5030e234ed
Tx public key: bef4af200d314ede00b06db3f3fccec90f4b9c70788506deb0c434a3d63e882a
Timestamp: 1578927248 Timestamp [UCT]: 2020-01-13 14:54:08 Age [y:d:h:m:s]: 04:349:06:47:07
Block: 44730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1139125 RingCT/type: yes/0
Extra: 01bef4af200d314ede00b06db3f3fccec90f4b9c70788506deb0c434a3d63e882a02110000000a8a2ee0d9000000000000000000

1 output(s) for total of 436.306599797000 dcy

stealth address amount amount idx
00: 44a7ec8d24f59c896a4195f8f0af10289092e1b9d85bc53cd8d91ba1b2e952f4 436.306599797000 81482 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": 44740, "vin": [ { "gen": { "height": 44730 } } ], "vout": [ { "amount": 436306599797, "target": { "key": "44a7ec8d24f59c896a4195f8f0af10289092e1b9d85bc53cd8d91ba1b2e952f4" } } ], "extra": [ 1, 190, 244, 175, 32, 13, 49, 78, 222, 0, 176, 109, 179, 243, 252, 206, 201, 15, 75, 156, 112, 120, 133, 6, 222, 176, 196, 52, 163, 214, 62, 136, 42, 2, 17, 0, 0, 0, 10, 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