Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 393d977a491be712c689a998c4d97bd9f4466189535d4c1a0788dde70fd6f571

Tx prefix hash: 67f2ed819990d7c5dd50f3368e57220f082d23f5c6f0cb0e9db3b3294570f3d6
Tx public key: dedd4f761e3d615da79360ba9bcbf111accfd66982af55e0ee3e9fc2f9655a26
Timestamp: 1658138565 Timestamp [UCT]: 2022-07-18 10:02:45 Age [y:d:h:m:s]: 02:259:12:19:57
Block: 546345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 706633 RingCT/type: yes/0
Extra: 01dedd4f761e3d615da79360ba9bcbf111accfd66982af55e0ee3e9fc2f9655a26021100000001faf35c9c000000000000000000

1 output(s) for total of 9.500191377000 dcy

stealth address amount amount idx
00: 3f66727775f95945ea3dde531d0ac21fa1aade84178807f2e3d3912a6b5ba3c7 9.500191377000 977350 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": 546355, "vin": [ { "gen": { "height": 546345 } } ], "vout": [ { "amount": 9500191377, "target": { "key": "3f66727775f95945ea3dde531d0ac21fa1aade84178807f2e3d3912a6b5ba3c7" } } ], "extra": [ 1, 222, 221, 79, 118, 30, 61, 97, 93, 167, 147, 96, 186, 155, 203, 241, 17, 172, 207, 214, 105, 130, 175, 85, 224, 238, 62, 159, 194, 249, 101, 90, 38, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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