Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2250350312bdb8100cda815e036dc47417743a5a0f8e00c2ed6a3d8da8f3e45d

Tx prefix hash: 5f6432fddfdb546fdf2351f82643601f0c03800d3f0ce778a93369f6b24b9098
Tx public key: 6d5a2df69162ed19fd82c1d368334a91f0d68301fd7611bd081923e57f8ed8a5
Timestamp: 1719440703 Timestamp [UCT]: 2024-06-26 22:25:03 Age [y:d:h:m:s]: 01:146:09:36:26
Block: 1052913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363195 RingCT/type: yes/0
Extra: 016d5a2df69162ed19fd82c1d368334a91f0d68301fd7611bd081923e57f8ed8a502110000000f59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16163733a3396300dd917955275f02b8e91d56a2779cd50a0c09b0767e82e9f9 0.600000000000 1523258 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": 1052923, "vin": [ { "gen": { "height": 1052913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16163733a3396300dd917955275f02b8e91d56a2779cd50a0c09b0767e82e9f9" } } ], "extra": [ 1, 109, 90, 45, 246, 145, 98, 237, 25, 253, 130, 193, 211, 104, 51, 74, 145, 240, 214, 131, 1, 253, 118, 17, 189, 8, 25, 35, 229, 127, 142, 216, 165, 2, 17, 0, 0, 0, 15, 89, 218, 211, 245, 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