Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d58d2589544107104cd771a1ce08be231a0721f42f788c8ff3d3d041a91478a2

Tx prefix hash: 86f34fa008b3da914d31df51c930dab75ca3ef2ea052d7cbd0664eb28d318bf3
Tx public key: 57c00a39d281d33e5d3c571c2662823f5438bc4e2ff23f450aa42f7d3c3404d4
Timestamp: 1725046205 Timestamp [UCT]: 2024-08-30 19:30:05 Age [y:d:h:m:s]: 00:285:18:22:36
Block: 1099391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204094 RingCT/type: yes/0
Extra: 0157c00a39d281d33e5d3c571c2662823f5438bc4e2ff23f450aa42f7d3c3404d4021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cbd35b7e3ba351d833297fb7969614ea90851d44332ef889edeafe4884bf633 0.600000000000 1575352 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": 1099401, "vin": [ { "gen": { "height": 1099391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cbd35b7e3ba351d833297fb7969614ea90851d44332ef889edeafe4884bf633" } } ], "extra": [ 1, 87, 192, 10, 57, 210, 129, 211, 62, 93, 60, 87, 28, 38, 98, 130, 63, 84, 56, 188, 78, 47, 242, 63, 69, 10, 164, 47, 125, 60, 52, 4, 212, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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