Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e5dd4ce6175f221b91610c079361af4520a295df021d3dac4d398c6411f0f93

Tx prefix hash: cdb4f5f0fd66d0cf5c43a7a36f2090e432c1c19bbfdfe015983f8ed14933ce46
Tx public key: b1dee316868e63ca30ab1834a5e9cd399cef7503e861484ea7be2814a090e7db
Timestamp: 1713834290 Timestamp [UCT]: 2024-04-23 01:04:50 Age [y:d:h:m:s]: 00:206:10:55:46
Block: 1006436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147793 RingCT/type: yes/0
Extra: 01b1dee316868e63ca30ab1834a5e9cd399cef7503e861484ea7be2814a090e7db0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50b6198dd15e7e41c2287896714fe8d9db623b21dab1af57dcf697df84fa2ad2 0.600000000000 1467470 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": 1006446, "vin": [ { "gen": { "height": 1006436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50b6198dd15e7e41c2287896714fe8d9db623b21dab1af57dcf697df84fa2ad2" } } ], "extra": [ 1, 177, 222, 227, 22, 134, 142, 99, 202, 48, 171, 24, 52, 165, 233, 205, 57, 156, 239, 117, 3, 232, 97, 72, 78, 167, 190, 40, 20, 160, 144, 231, 219, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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