Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eef48ee652e6fb7b4a789c9c1bb8e87b0a89129c0aa3d2183cd9673ef3510acd

Tx prefix hash: 5a332ccb83efc66517546167066b1c17f9f12a202608aa8e68953281096fcc65
Tx public key: 36d2d412fba08ad4b5223900ae5115ef416dd50c95dddbc1a8a3c0d1ef7226a9
Timestamp: 1722961750 Timestamp [UCT]: 2024-08-06 16:29:10 Age [y:d:h:m:s]: 00:200:16:59:29
Block: 1082106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143300 RingCT/type: yes/0
Extra: 0136d2d412fba08ad4b5223900ae5115ef416dd50c95dddbc1a8a3c0d1ef7226a9021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7adcafa658f0309df24bf24748c8c3c370335a700a011cdf197e9a680323fdf3 0.600000000000 1555929 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": 1082116, "vin": [ { "gen": { "height": 1082106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7adcafa658f0309df24bf24748c8c3c370335a700a011cdf197e9a680323fdf3" } } ], "extra": [ 1, 54, 210, 212, 18, 251, 160, 138, 212, 181, 34, 57, 0, 174, 81, 21, 239, 65, 109, 213, 12, 149, 221, 219, 193, 168, 163, 192, 209, 239, 114, 38, 169, 2, 17, 0, 0, 0, 5, 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