Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c125cb968af0ddb9e0bfaad7fb802ce0eeab87a0e9d1b62eeb695f2b7af58c1

Tx prefix hash: dd0d7725d9b1accb45395c6397f063dc51fa9cd07237460e2bd28070df936d56
Tx public key: 09c1f57e7025e27e798b832502c8913503908c164e8875550a9661c7f1c68796
Timestamp: 1725159163 Timestamp [UCT]: 2024-09-01 02:52:43 Age [y:d:h:m:s]: 00:144:16:02:26
Block: 1100321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103439 RingCT/type: yes/0
Extra: 0109c1f57e7025e27e798b832502c8913503908c164e8875550a9661c7f1c68796021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88e430e5003ce15dc92b7644560e2e24ec28e320e10697f6dd6b823c2d73a329 0.600000000000 1576296 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": 1100331, "vin": [ { "gen": { "height": 1100321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88e430e5003ce15dc92b7644560e2e24ec28e320e10697f6dd6b823c2d73a329" } } ], "extra": [ 1, 9, 193, 245, 126, 112, 37, 226, 126, 121, 139, 131, 37, 2, 200, 145, 53, 3, 144, 140, 22, 78, 136, 117, 85, 10, 150, 97, 199, 241, 198, 135, 150, 2, 17, 0, 0, 0, 4, 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