Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d61c1998a60d1f9278969ec8c286c1695ac802535ecf799c56a755cf3cf38b2

Tx prefix hash: 59829362424c704e5db1e7a3ef31848c6a2cab2c5c2e76af8b19914faf5c942d
Tx public key: 7eb5d29062231a9ec36d91069fa0a9914f3e1b62b24ddf60d04a9217f49a64a2
Timestamp: 1704340774 Timestamp [UCT]: 2024-01-04 03:59:34 Age [y:d:h:m:s]: 01:112:10:35:24
Block: 927732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341480 RingCT/type: yes/0
Extra: 017eb5d29062231a9ec36d91069fa0a9914f3e1b62b24ddf60d04a9217f49a64a202110000000741ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0102f98d45d84f7de3d42604e2de2048513af6be6b387302580e27413754dbe1 0.600000000000 1385568 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": 927742, "vin": [ { "gen": { "height": 927732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0102f98d45d84f7de3d42604e2de2048513af6be6b387302580e27413754dbe1" } } ], "extra": [ 1, 126, 181, 210, 144, 98, 35, 26, 158, 195, 109, 145, 6, 159, 160, 169, 145, 79, 62, 27, 98, 178, 77, 223, 96, 208, 74, 146, 23, 244, 154, 100, 162, 2, 17, 0, 0, 0, 7, 65, 238, 28, 155, 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