Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63182af630b643b89b24dc9adce3a530bc1b190bdddafe12d4715f91ea9992df

Tx prefix hash: b97cece5d93aee2d94ca36e16aeee3ab316244c1ab84099f86e3cce2d6bd61ac
Tx public key: ffa2c91d39963b8abf7d23826c518183073c045cfa49bf37019bfdd94479e662
Timestamp: 1684148608 Timestamp [UCT]: 2023-05-15 11:03:28 Age [y:d:h:m:s]: 01:339:08:57:47
Block: 760577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503788 RingCT/type: yes/0
Extra: 01ffa2c91d39963b8abf7d23826c518183073c045cfa49bf37019bfdd94479e662021100000007e6d27f9c000000000000000000

1 output(s) for total of 1.870394399000 dcy

stealth address amount amount idx
00: 75c4d1d026893ce9a1a6696662490aa2064394d945c3b1f8a8e64be58d666be1 1.870394399000 1209194 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": 760587, "vin": [ { "gen": { "height": 760577 } } ], "vout": [ { "amount": 1870394399, "target": { "key": "75c4d1d026893ce9a1a6696662490aa2064394d945c3b1f8a8e64be58d666be1" } } ], "extra": [ 1, 255, 162, 201, 29, 57, 150, 59, 138, 191, 125, 35, 130, 108, 81, 129, 131, 7, 60, 4, 92, 250, 73, 191, 55, 1, 155, 253, 217, 68, 121, 230, 98, 2, 17, 0, 0, 0, 7, 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