Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a4a550f470c344410a332a8fa064c2d19f4e4000fa9e6701b791f16ae22e686

Tx prefix hash: 50bcaa3ac447c55830b646bfca4b0277fdd5103a4b303a59c74455050cd708f8
Tx public key: 7b1a37794aef2e27e85c27d8abce5f0d20a2f0f173e11cfa53f61515e894348e
Timestamp: 1717518602 Timestamp [UCT]: 2024-06-04 16:30:02 Age [y:d:h:m:s]: 00:284:10:32:29
Block: 1036991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203279 RingCT/type: yes/0
Extra: 017b1a37794aef2e27e85c27d8abce5f0d20a2f0f173e11cfa53f61515e894348e0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b893cf5610b7d1fbe031271db8c089938c0945ed3ef2f944547c8da26ef4e09 0.600000000000 1505522 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": 1037001, "vin": [ { "gen": { "height": 1036991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b893cf5610b7d1fbe031271db8c089938c0945ed3ef2f944547c8da26ef4e09" } } ], "extra": [ 1, 123, 26, 55, 121, 74, 239, 46, 39, 232, 92, 39, 216, 171, 206, 95, 13, 32, 162, 240, 241, 115, 225, 28, 250, 83, 246, 21, 21, 232, 148, 52, 142, 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