Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88e3d7e854304d2de3aa9ec8dcd44ef5913f986f5d3a434116b3b34c15d3623c

Tx prefix hash: 61aca09a2644031fbc7c377c3863a5a112b8eccbb57042364de0646cb1bc1bf6
Tx public key: 9dc9f61ad9ed24a351c8d4bae51262b4c3181b2dcf8cb496750a559f7937356a
Timestamp: 1720381593 Timestamp [UCT]: 2024-07-07 19:46:33 Age [y:d:h:m:s]: 00:273:11:11:31
Block: 1060715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195386 RingCT/type: yes/0
Extra: 019dc9f61ad9ed24a351c8d4bae51262b4c3181b2dcf8cb496750a559f7937356a0211000000048fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33eade4f98a1e8b475fc433212dc599f09b967544276af367fedbb0dc33448a2 0.600000000000 1531200 of 15

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": 1060725, "vin": [ { "gen": { "height": 1060715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33eade4f98a1e8b475fc433212dc599f09b967544276af367fedbb0dc33448a2" } } ], "extra": [ 1, 157, 201, 246, 26, 217, 237, 36, 163, 81, 200, 212, 186, 229, 18, 98, 180, 195, 24, 27, 45, 207, 140, 180, 150, 117, 10, 85, 159, 121, 55, 53, 106, 2, 17, 0, 0, 0, 4, 143, 218, 155, 45, 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