Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 792f7d1df47c3ae93f51f29b2b6b4871112c3152da68a0ff025202fd293bb8f5

Tx prefix hash: 1c73f5fa03bdeab7e58a4a8cf42d1dca05b226e79a7dd63fb0ed6dc8308707ac
Tx public key: 0ab76e30867df1d2c6797967e09617dc1cdd8909daff7d27a71a2155d6e677c1
Timestamp: 1718007243 Timestamp [UCT]: 2024-06-10 08:14:03 Age [y:d:h:m:s]: 00:143:01:12:26
Block: 1041036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102401 RingCT/type: yes/0
Extra: 010ab76e30867df1d2c6797967e09617dc1cdd8909daff7d27a71a2155d6e677c10211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ecfd98efd64d733a761076f4b024ac2b85c7c9248d0af3e1abdfdcb892ed0b3 0.600000000000 1509701 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": 1041046, "vin": [ { "gen": { "height": 1041036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ecfd98efd64d733a761076f4b024ac2b85c7c9248d0af3e1abdfdcb892ed0b3" } } ], "extra": [ 1, 10, 183, 110, 48, 134, 125, 241, 210, 198, 121, 121, 103, 224, 150, 23, 220, 28, 221, 137, 9, 218, 255, 125, 39, 167, 26, 33, 85, 214, 230, 119, 193, 2, 17, 0, 0, 0, 1, 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