Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c327983265cbbe145eb541e949dc1fb62fd450ea539b0c85198361e404b7cd9

Tx prefix hash: 0e52314d5fcd8c03adc22ca44b8929d92e4369410ee2c0a948bf8df430aa9af5
Tx public key: 11f389d2cd21d6f568e11a1f823eacb57ebc3f782fb6795d57a987559f6514fe
Timestamp: 1711986003 Timestamp [UCT]: 2024-04-01 15:40:03 Age [y:d:h:m:s]: 01:232:05:18:21
Block: 991075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424703 RingCT/type: yes/0
Extra: 0111f389d2cd21d6f568e11a1f823eacb57ebc3f782fb6795d57a987559f6514fe02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a2e8fe9fda802890a86aca7685d0bae3674b504d56ba85ec445078dc448f897 0.600000000000 1451409 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": 991085, "vin": [ { "gen": { "height": 991075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a2e8fe9fda802890a86aca7685d0bae3674b504d56ba85ec445078dc448f897" } } ], "extra": [ 1, 17, 243, 137, 210, 205, 33, 214, 245, 104, 225, 26, 31, 130, 62, 172, 181, 126, 188, 63, 120, 47, 182, 121, 93, 87, 169, 135, 85, 159, 101, 20, 254, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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