Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c9b9143b1e4b3a47d7974b4d9ce61461349af9e8a576f9c04da44e67a6147b2

Tx prefix hash: df7c5265c48967216a12bf8f9d47b2bf3476d25d2958486c40516bfff2811966
Tx public key: bd3c10e39cd3e30e88933ecabc940f3888c80fe2223665cd063fc7f3a941a7cc
Timestamp: 1648259085 Timestamp [UCT]: 2022-03-26 01:44:45 Age [y:d:h:m:s]: 03:220:21:51:05
Block: 466484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 935775 RingCT/type: yes/0
Extra: 01bd3c10e39cd3e30e88933ecabc940f3888c80fe2223665cd063fc7f3a941a7cc0211000000054a0f5013000000000000000000

1 output(s) for total of 17.472100371000 dcy

stealth address amount amount idx
00: 63cf79faa189d74aacf2d2c39fe4f9253b0995b571b34dff9632c6b1fbfc49b4 17.472100371000 884807 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": 466494, "vin": [ { "gen": { "height": 466484 } } ], "vout": [ { "amount": 17472100371, "target": { "key": "63cf79faa189d74aacf2d2c39fe4f9253b0995b571b34dff9632c6b1fbfc49b4" } } ], "extra": [ 1, 189, 60, 16, 227, 156, 211, 227, 14, 136, 147, 62, 202, 188, 148, 15, 56, 136, 200, 15, 226, 34, 54, 101, 205, 6, 63, 199, 243, 169, 65, 167, 204, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 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