Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dd939557773ee05a86fd717f3793849b44cff33b9ea2b7c09643fb27d66edd6

Tx prefix hash: 55a5be148ce68f53132e05c3f261f46fc2a91ccce344e855879db1a013d1116c
Tx public key: bf8326e234c58bea54d2e088bd72fe980a70fcb7ca50e061dfca66bb99d3fcf1
Timestamp: 1736947804 Timestamp [UCT]: 2025-01-15 13:30:04 Age [y:d:h:m:s]: 00:153:22:47:03
Block: 1197915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109738 RingCT/type: yes/0
Extra: 01bf8326e234c58bea54d2e088bd72fe980a70fcb7ca50e061dfca66bb99d3fcf10211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a4c2ef8147db1b0a2fe603aba2ea35c84d9c69547d7be3241d55f8fcc0a4711 0.600000000000 1684532 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": 1197925, "vin": [ { "gen": { "height": 1197915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a4c2ef8147db1b0a2fe603aba2ea35c84d9c69547d7be3241d55f8fcc0a4711" } } ], "extra": [ 1, 191, 131, 38, 226, 52, 197, 139, 234, 84, 210, 224, 136, 189, 114, 254, 152, 10, 112, 252, 183, 202, 80, 224, 97, 223, 202, 102, 187, 153, 211, 252, 241, 2, 17, 0, 0, 0, 2, 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