Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 191439c5c44804a928523a212e5782b49da2c4b4398dc9f1ad4d3f249f21c390

Tx prefix hash: f3e6546734a846c3a3f72f728f8bb298359d5f5d859baf62c3bf4c0b80f2a260
Tx public key: 44a8cb98ef5d456260d660257b5c430c2bb63215e5217ccb05afb371f6a24321
Timestamp: 1710235240 Timestamp [UCT]: 2024-03-12 09:20:40 Age [y:d:h:m:s]: 00:285:21:12:13
Block: 976616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204675 RingCT/type: yes/0
Extra: 0144a8cb98ef5d456260d660257b5c430c2bb63215e5217ccb05afb371f6a243210211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bf735be25dc5f548315750d9542f4b803a87c28d2f034de8230c0e4a9c1ed78 0.600000000000 1436611 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": 976626, "vin": [ { "gen": { "height": 976616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bf735be25dc5f548315750d9542f4b803a87c28d2f034de8230c0e4a9c1ed78" } } ], "extra": [ 1, 68, 168, 203, 152, 239, 93, 69, 98, 96, 214, 96, 37, 123, 92, 67, 12, 43, 182, 50, 21, 229, 33, 124, 203, 5, 175, 179, 113, 246, 162, 67, 33, 2, 17, 0, 0, 0, 5, 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