Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e03309e2a48f88b652e1d9931017f8f4b80fa58397c5c97143e1519adb9c5194

Tx prefix hash: 64c4c9c971045f9eb2702e2c79f1971faa15f2e1109301dd5be98148adbed283
Tx public key: 68e98f6ba2bf526067a0afeb184d547258c94b351fdf692996f363f7e6279ff0
Timestamp: 1685440752 Timestamp [UCT]: 2023-05-30 09:59:12 Age [y:d:h:m:s]: 01:344:11:31:44
Block: 771297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507403 RingCT/type: yes/0
Extra: 0168e98f6ba2bf526067a0afeb184d547258c94b351fdf692996f363f7e6279ff002110000000175e3f0e9000000000000000000

1 output(s) for total of 1.707548431000 dcy

stealth address amount amount idx
00: d375ed9fa2ac8ddb68876aaca2ae9cedd32b7a053476df1f8b57c57fe919cb1e 1.707548431000 1220648 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": 771307, "vin": [ { "gen": { "height": 771297 } } ], "vout": [ { "amount": 1707548431, "target": { "key": "d375ed9fa2ac8ddb68876aaca2ae9cedd32b7a053476df1f8b57c57fe919cb1e" } } ], "extra": [ 1, 104, 233, 143, 107, 162, 191, 82, 96, 103, 160, 175, 235, 24, 77, 84, 114, 88, 201, 75, 53, 31, 223, 105, 41, 150, 243, 99, 247, 230, 39, 159, 240, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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