Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88bb4a036b838b61f102ba0b7cff9bb9c63553783c6548afad040948164326e0

Tx prefix hash: 5c584eeb5067556b153d7bd399e3734f7a2a0df3d26cc548db7a079da0fa4d50
Tx public key: 4ad5748d09f5c0578fe5d990db731c5506a81308dce1f082f7b486a7ace0e24c
Timestamp: 1736991279 Timestamp [UCT]: 2025-01-16 01:34:39 Age [y:d:h:m:s]: 00:060:09:37:47
Block: 1198272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42962 RingCT/type: yes/0
Extra: 014ad5748d09f5c0578fe5d990db731c5506a81308dce1f082f7b486a7ace0e24c021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e4b56832e34a7bfa14142b175f0221ceaff3d3680a0c3aeb11bb9ba1941b1f0 0.600000000000 1684893 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": 1198282, "vin": [ { "gen": { "height": 1198272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e4b56832e34a7bfa14142b175f0221ceaff3d3680a0c3aeb11bb9ba1941b1f0" } } ], "extra": [ 1, 74, 213, 116, 141, 9, 245, 192, 87, 143, 229, 217, 144, 219, 115, 28, 85, 6, 168, 19, 8, 220, 225, 240, 130, 247, 180, 134, 167, 172, 224, 226, 76, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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