Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a719b9d1d32cdd33e10dba3eb70a7ad10c7e70e0bae70c7d90be77e7687dc93b

Tx prefix hash: 7e6913e5b08c760db507e92467cce2e0cbb71627ef4c56ceff6977773b879df3
Tx public key: dff8918c525f3a03f38cac84e5678e53056b29bc06ce2221ee42b89246bdafd0
Timestamp: 1706525629 Timestamp [UCT]: 2024-01-29 10:53:49 Age [y:d:h:m:s]: 01:095:06:11:52
Block: 945824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329179 RingCT/type: yes/0
Extra: 01dff8918c525f3a03f38cac84e5678e53056b29bc06ce2221ee42b89246bdafd002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3fedd56f2b5fb602fd009f6c4f58d0d01c1b0a0cae793ca2072de609e2695ef 0.600000000000 1404148 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": 945834, "vin": [ { "gen": { "height": 945824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3fedd56f2b5fb602fd009f6c4f58d0d01c1b0a0cae793ca2072de609e2695ef" } } ], "extra": [ 1, 223, 248, 145, 140, 82, 95, 58, 3, 243, 140, 172, 132, 229, 103, 142, 83, 5, 107, 41, 188, 6, 206, 34, 33, 238, 66, 184, 146, 70, 189, 175, 208, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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