Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52d2b599cb13397312f8bf980aab0a10a8c0632fe90579e9a8dbf4b79ad225cd

Tx prefix hash: 50e4e5f69c492c1369d6398e22bacaf9a2c67dfd4819976d39fd1b531c42f297
Tx public key: f5b9a8a8caedbf2b416a94d5e6e9f9be58b4541081f5ed2f55e6b83102019a7a
Timestamp: 1766269395 Timestamp [UCT]: 2025-12-20 22:23:15 Age [y:d:h:m:s]: 00:001:11:40:40
Block: 1438019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1054 RingCT/type: yes/0
Extra: 01f5b9a8a8caedbf2b416a94d5e6e9f9be58b4541081f5ed2f55e6b83102019a7a0211000000047b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e2aba11f051aee8c4d82833cdb18642840f6f3d1d9e3cd3afe2baf6f41c48d7 0.600000000000 1926834 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": 1438029, "vin": [ { "gen": { "height": 1438019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e2aba11f051aee8c4d82833cdb18642840f6f3d1d9e3cd3afe2baf6f41c48d7" } } ], "extra": [ 1, 245, 185, 168, 168, 202, 237, 191, 43, 65, 106, 148, 213, 230, 233, 249, 190, 88, 180, 84, 16, 129, 245, 237, 47, 85, 230, 184, 49, 2, 1, 154, 122, 2, 17, 0, 0, 0, 4, 123, 30, 81, 172, 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