Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9933899722470c7270aa540bc3c5f010b7e242d0c0fc4b6edc35436d2f9b497

Tx prefix hash: cd2f35bac8e54c4119702eb6be3c18ee7304e1fc6d09484bd478e3d894486e37
Tx public key: c6ce3ff7e305146cb1e7052888d2e9bba785cd579a5d803649b3519f412c1db7
Timestamp: 1705184092 Timestamp [UCT]: 2024-01-13 22:14:52 Age [y:d:h:m:s]: 00:344:08:38:08
Block: 934710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246588 RingCT/type: yes/0
Extra: 01c6ce3ff7e305146cb1e7052888d2e9bba785cd579a5d803649b3519f412c1db70211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0b141e2f9d1a0bdcaa2c6960877a10d05add5bb13f6db01000d8c0acf370cb9 0.600000000000 1392726 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": 934720, "vin": [ { "gen": { "height": 934710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0b141e2f9d1a0bdcaa2c6960877a10d05add5bb13f6db01000d8c0acf370cb9" } } ], "extra": [ 1, 198, 206, 63, 247, 227, 5, 20, 108, 177, 231, 5, 40, 136, 210, 233, 187, 167, 133, 205, 87, 154, 93, 128, 54, 73, 179, 81, 159, 65, 44, 29, 183, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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