Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 882e7d263aa9c376bf6d777a615935e9dc7519ccc0cf32fda83fd3fec18f0776

Tx prefix hash: d1aec7164497f926cebf287b66bbf560ffaf460fb0def172ae3d872adc009826
Tx public key: 2e82892a5041b336aecc068d6776e1823923ec76c0f312bee40d28e5e30a5d20
Timestamp: 1740776085 Timestamp [UCT]: 2025-02-28 20:54:45 Age [y:d:h:m:s]: 00:264:20:49:40
Block: 1229331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187058 RingCT/type: yes/0
Extra: 012e82892a5041b336aecc068d6776e1823923ec76c0f312bee40d28e5e30a5d200211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b35a2a5388e865b006648d3fc393c59a37e50ad72433de3843b07a11e7b42f5 0.600000000000 1716216 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": 1229341, "vin": [ { "gen": { "height": 1229331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b35a2a5388e865b006648d3fc393c59a37e50ad72433de3843b07a11e7b42f5" } } ], "extra": [ 1, 46, 130, 137, 42, 80, 65, 179, 54, 174, 204, 6, 141, 103, 118, 225, 130, 57, 35, 236, 118, 192, 243, 18, 190, 228, 13, 40, 229, 227, 10, 93, 32, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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