Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbfc8e021dcf6c6a772ce5b3fb2a22434d7be423f70cbe03c0ebfa54f75f1ce6

Tx prefix hash: 9e4ffde44e6075150537ae8c5dc629e6b99b482edbea280ec6f913a6b656f8a4
Tx public key: f7d2a316916663249cfbde948d84ba462e22205f5fb7287e8541093003288c1d
Timestamp: 1580571056 Timestamp [UCT]: 2020-02-01 15:30:56 Age [y:d:h:m:s]: 05:084:03:34:22
Block: 56715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1211912 RingCT/type: yes/0
Extra: 01f7d2a316916663249cfbde948d84ba462e22205f5fb7287e8541093003288c1d021100000002b221b3d1000000000000000000

1 output(s) for total of 398.180955687000 dcy

stealth address amount amount idx
00: 3586b68bad81bed24c3fab0f67480446280476033e0047fd70ab0067c8015549 398.180955687000 104516 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": 56725, "vin": [ { "gen": { "height": 56715 } } ], "vout": [ { "amount": 398180955687, "target": { "key": "3586b68bad81bed24c3fab0f67480446280476033e0047fd70ab0067c8015549" } } ], "extra": [ 1, 247, 210, 163, 22, 145, 102, 99, 36, 156, 251, 222, 148, 141, 132, 186, 70, 46, 34, 32, 95, 95, 183, 40, 126, 133, 65, 9, 48, 3, 40, 140, 29, 2, 17, 0, 0, 0, 2, 178, 33, 179, 209, 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