Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 653bc083bb08a6abf2d54766bdfcd94353e35f834232cef4fcfa7090278a14a3

Tx prefix hash: 2d836176c48df9165e484f10e9a279ac2c8b027a551de362c85896cf00899f00
Tx public key: 128a11af1f399f654642f69e02a31d436e52c8c144c5e0e56cddd1dbbd6e501e
Timestamp: 1676415486 Timestamp [UCT]: 2023-02-14 22:58:06 Age [y:d:h:m:s]: 01:314:03:00:02
Block: 697111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485457 RingCT/type: yes/0
Extra: 01128a11af1f399f654642f69e02a31d436e52c8c144c5e0e56cddd1dbbd6e501e0211000000045029cbac000000000000000000

1 output(s) for total of 3.007334870000 dcy

stealth address amount amount idx
00: 69bcaa0cdaac2d7451ed4d7feb07e9e1b025956093d883f1a47d17875c48f5df 3.007334870000 1140208 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": 697121, "vin": [ { "gen": { "height": 697111 } } ], "vout": [ { "amount": 3007334870, "target": { "key": "69bcaa0cdaac2d7451ed4d7feb07e9e1b025956093d883f1a47d17875c48f5df" } } ], "extra": [ 1, 18, 138, 17, 175, 31, 57, 159, 101, 70, 66, 246, 158, 2, 163, 29, 67, 110, 82, 200, 193, 68, 197, 224, 229, 108, 221, 209, 219, 189, 110, 80, 30, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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