Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1d3cd1ae2416d7b687b25f5dce561f3bcb4196c31f9cf5bed0ff248e48d413d

Tx prefix hash: 67c2c6b67cf146c52c3d2edf781e9750c6d296e5a034b9cbb873a8a2e17292eb
Tx public key: a673d8f0104ea0678b77e011f8ac030a07eb4c055b044c3a5951ad28bf5111cb
Timestamp: 1583092771 Timestamp [UCT]: 2020-03-01 19:59:31 Age [y:d:h:m:s]: 04:249:17:40:44
Block: 74972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1072146 RingCT/type: yes/0
Extra: 01a673d8f0104ea0678b77e011f8ac030a07eb4c055b044c3a5951ad28bf5111cb0211000000b003d36d11000000000000000000

1 output(s) for total of 346.407621787000 dcy

stealth address amount amount idx
00: 40e940ea7dce8c7d2bf63c2f8b58cc8c16edcb34bbd50ad0ff3ca942117f072c 346.407621787000 138586 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": 74982, "vin": [ { "gen": { "height": 74972 } } ], "vout": [ { "amount": 346407621787, "target": { "key": "40e940ea7dce8c7d2bf63c2f8b58cc8c16edcb34bbd50ad0ff3ca942117f072c" } } ], "extra": [ 1, 166, 115, 216, 240, 16, 78, 160, 103, 139, 119, 224, 17, 248, 172, 3, 10, 7, 235, 76, 5, 91, 4, 76, 58, 89, 81, 173, 40, 191, 81, 17, 203, 2, 17, 0, 0, 0, 176, 3, 211, 109, 17, 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