Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b4fdb2267ac5a679f154cfe12c426fce26b78de7f6f85cf3a744342cb4f5a5a

Tx prefix hash: bf42c286f680159f32dd23875eba6a75907646ac28f4f6ea4008921e82c36186
Tx public key: 958ef263c77a9191c53d6fc4ee8bcc7344552e89ff3d6019ba42f1d4a538bfc5
Timestamp: 1648841859 Timestamp [UCT]: 2022-04-01 19:37:39 Age [y:d:h:m:s]: 02:284:02:06:17
Block: 471130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 722741 RingCT/type: yes/0
Extra: 01958ef263c77a9191c53d6fc4ee8bcc7344552e89ff3d6019ba42f1d4a538bfc502110000000337cb3088000000000000000000

1 output(s) for total of 16.863826798000 dcy

stealth address amount amount idx
00: f569413b70463235d15aa39c82f68f64c91278465c8b4e72bf8be87f3a1dbfd4 16.863826798000 890410 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": 471140, "vin": [ { "gen": { "height": 471130 } } ], "vout": [ { "amount": 16863826798, "target": { "key": "f569413b70463235d15aa39c82f68f64c91278465c8b4e72bf8be87f3a1dbfd4" } } ], "extra": [ 1, 149, 142, 242, 99, 199, 122, 145, 145, 197, 61, 111, 196, 238, 139, 204, 115, 68, 85, 46, 137, 255, 61, 96, 25, 186, 66, 241, 212, 165, 56, 191, 197, 2, 17, 0, 0, 0, 3, 55, 203, 48, 136, 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