Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17a47164b01dfa1e901a75589fcfb6aac49192e9a0823de955aa782b203b0e3b

Tx prefix hash: 9db016a2f83189f87a205a93e2d006d4fd38f141e62b7432ad46bd0f403a8e34
Tx public key: 6cdfbebe095f7ff45a8805dbb5edb6cb143813e892b002e75c63aff46653e635
Timestamp: 1580481203 Timestamp [UCT]: 2020-01-31 14:33:23 Age [y:d:h:m:s]: 04:327:17:14:51
Block: 55852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125482 RingCT/type: yes/0
Extra: 016cdfbebe095f7ff45a8805dbb5edb6cb143813e892b002e75c63aff46653e635021100000003391a8d0e000000000000000000

1 output(s) for total of 400.811305651000 dcy

stealth address amount amount idx
00: eb75c796580ec4a2ffe9e65d58b580e44a470e1d1197ce0e05216696b8439268 400.811305651000 103041 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": 55862, "vin": [ { "gen": { "height": 55852 } } ], "vout": [ { "amount": 400811305651, "target": { "key": "eb75c796580ec4a2ffe9e65d58b580e44a470e1d1197ce0e05216696b8439268" } } ], "extra": [ 1, 108, 223, 190, 190, 9, 95, 127, 244, 90, 136, 5, 219, 181, 237, 182, 203, 20, 56, 19, 232, 146, 176, 2, 231, 92, 99, 175, 244, 102, 83, 230, 53, 2, 17, 0, 0, 0, 3, 57, 26, 141, 14, 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