Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60a52692264e6594e30074d9eb06656ac53b25ee528b784ddb4150e658fb7e12

Tx prefix hash: 4497ce8a5d43fabeae7d449fdc6ca0dd672500cd5df79dc482ca94965d4f84ea
Tx public key: cb54d8d8e9106b71a7e56738b4fb664c86bf2ae0338fb8e5be4e1ff2286400a8
Timestamp: 1649427612 Timestamp [UCT]: 2022-04-08 14:20:12 Age [y:d:h:m:s]: 03:038:10:24:59
Block: 475889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 807924 RingCT/type: yes/0
Extra: 01cb54d8d8e9106b71a7e56738b4fb664c86bf2ae0338fb8e5be4e1ff2286400a80211000000024da16a3a000000000000000000

1 output(s) for total of 16.262317391000 dcy

stealth address amount amount idx
00: a17d7644bcd947f88460aef9329c778c6eda447f294e43c70d2b907b6c315b57 16.262317391000 896230 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": 475899, "vin": [ { "gen": { "height": 475889 } } ], "vout": [ { "amount": 16262317391, "target": { "key": "a17d7644bcd947f88460aef9329c778c6eda447f294e43c70d2b907b6c315b57" } } ], "extra": [ 1, 203, 84, 216, 216, 233, 16, 107, 113, 167, 229, 103, 56, 180, 251, 102, 76, 134, 191, 42, 224, 51, 143, 184, 229, 190, 78, 31, 242, 40, 100, 0, 168, 2, 17, 0, 0, 0, 2, 77, 161, 106, 58, 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