Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31d38572627a089c06ea45e05fa01fc7756f76e8eb80032cc4f96df97c6d277c

Tx prefix hash: 61cbe8ed5014212326b40a4ee5eaa733317f3212ccde2689f01a500da0688074
Tx public key: 3d01b7686a6337e9f12a4bbf2bede5e9b93b31ed3a1d053458ddee480737ce81
Timestamp: 1699416156 Timestamp [UCT]: 2023-11-08 04:02:36 Age [y:d:h:m:s]: 01:167:21:47:29
Block: 886910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381195 RingCT/type: yes/0
Extra: 013d01b7686a6337e9f12a4bbf2bede5e9b93b31ed3a1d053458ddee480737ce81021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.706804000000 dcy

stealth address amount amount idx
00: 5adf04dda20f9ab74f66db68edf2fbad6f2f679bafd1b472c485e050c7d3886e 0.706804000000 1342757 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": 886920, "vin": [ { "gen": { "height": 886910 } } ], "vout": [ { "amount": 706804000, "target": { "key": "5adf04dda20f9ab74f66db68edf2fbad6f2f679bafd1b472c485e050c7d3886e" } } ], "extra": [ 1, 61, 1, 183, 104, 106, 99, 55, 233, 241, 42, 75, 191, 43, 237, 229, 233, 185, 59, 49, 237, 58, 29, 5, 52, 88, 221, 238, 72, 7, 55, 206, 129, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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