Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 917effcc028d0d745b0fd2b48d9a2028c074b600d434dd0f7c9de82fef73914f

Tx prefix hash: 3b1824e04fb20a22c80eb8f1442cd31c492d145433237e932c372ad49a53ee48
Tx public key: 011240466e3952bb6e5e241e5f1700dbb3fdf8c3dfab05413b1d7651bd91c946
Timestamp: 1763489136 Timestamp [UCT]: 2025-11-18 18:05:36 Age [y:d:h:m:s]: 00:009:12:18:12
Block: 1414980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6807 RingCT/type: yes/0
Extra: 01011240466e3952bb6e5e241e5f1700dbb3fdf8c3dfab05413b1d7651bd91c9460211000000018ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e3c030e07c73b8e4f61e0c6078d51fa67806d04ccedb820c210d657fdefc74a 0.600000000000 1903473 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": 1414990, "vin": [ { "gen": { "height": 1414980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e3c030e07c73b8e4f61e0c6078d51fa67806d04ccedb820c210d657fdefc74a" } } ], "extra": [ 1, 1, 18, 64, 70, 110, 57, 82, 187, 110, 94, 36, 30, 95, 23, 0, 219, 179, 253, 248, 195, 223, 171, 5, 65, 59, 29, 118, 81, 189, 145, 201, 70, 2, 17, 0, 0, 0, 1, 140, 235, 127, 9, 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