Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bb74db3a268c7ed1b22aa8581f8fcd8b079bfcda19ff707a093ac86f0609e00

Tx prefix hash: f9f98b866d209417843318d1d3e22274b91aaf5f420b3de5c2da2cc8f5518608
Tx public key: 1c8b71ab0fc8ffea4d52f5e642eb213a2264f0ad4220e59dade99638c701f8b5
Timestamp: 1709385410 Timestamp [UCT]: 2024-03-02 13:16:50 Age [y:d:h:m:s]: 01:037:05:10:46
Block: 969558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287597 RingCT/type: yes/0
Extra: 011c8b71ab0fc8ffea4d52f5e642eb213a2264f0ad4220e59dade99638c701f8b50211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5f0da39ad18b8e363e8b9230fb5c0e03d90b0ca31c7afad3ba3086a4b082864 0.600000000000 1429395 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": 969568, "vin": [ { "gen": { "height": 969558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5f0da39ad18b8e363e8b9230fb5c0e03d90b0ca31c7afad3ba3086a4b082864" } } ], "extra": [ 1, 28, 139, 113, 171, 15, 200, 255, 234, 77, 82, 245, 230, 66, 235, 33, 58, 34, 100, 240, 173, 66, 32, 229, 157, 173, 233, 150, 56, 199, 1, 248, 181, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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