Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 563163085d8c3674c813a2a80c2be6aaa1f9291bec95fa326f5018fc5570dcfe

Tx prefix hash: b07764ac74f623b79569f2c0a0d50fb90d5929b88269f05cc0218a2dea75d6dd
Tx public key: 26f0b1c3830a96d402c2e9261c9a596cb2620d19e20db9a049a6cd6cf7f81169
Timestamp: 1748918138 Timestamp [UCT]: 2025-06-03 02:35:38 Age [y:d:h:m:s]: 00:214:18:00:54
Block: 1296762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151239 RingCT/type: yes/0
Extra: 0126f0b1c3830a96d402c2e9261c9a596cb2620d19e20db9a049a6cd6cf7f8116902110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 541705c65f11af070d6afd66149745a2d04d817d1aa6f4b16e486e6b42a4f2d7 0.600000000000 1784277 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": 1296772, "vin": [ { "gen": { "height": 1296762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "541705c65f11af070d6afd66149745a2d04d817d1aa6f4b16e486e6b42a4f2d7" } } ], "extra": [ 1, 38, 240, 177, 195, 131, 10, 150, 212, 2, 194, 233, 38, 28, 154, 89, 108, 178, 98, 13, 25, 226, 13, 185, 160, 73, 166, 205, 108, 247, 248, 17, 105, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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