Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94d564963cd818b508c751c67484f8315e81ccd74644a555789e708cf3275e90

Tx prefix hash: 4f6e4d47989a4d8ff4ac9c551fe9af56a8bf3c0adf9ba98ba69957a3c872846d
Tx public key: 7890854c6b6dfca57960d055d5a2c8524c1d3c94bfb383eab5e75c1849de1f23
Timestamp: 1706239056 Timestamp [UCT]: 2024-01-26 03:17:36 Age [y:d:h:m:s]: 01:124:00:31:11
Block: 943436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349784 RingCT/type: yes/0
Extra: 017890854c6b6dfca57960d055d5a2c8524c1d3c94bfb383eab5e75c1849de1f2302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8906dab325c501cbce1eb191281de316362d562c91fd7eb77e59b4a7af71c272 0.600000000000 1401642 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": 943446, "vin": [ { "gen": { "height": 943436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8906dab325c501cbce1eb191281de316362d562c91fd7eb77e59b4a7af71c272" } } ], "extra": [ 1, 120, 144, 133, 76, 107, 109, 252, 165, 121, 96, 208, 85, 213, 162, 200, 82, 76, 29, 60, 148, 191, 179, 131, 234, 181, 231, 92, 24, 73, 222, 31, 35, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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