Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0376d1e4042a1b9589be73cfb440e80e9b09de8ae749c1712684d4b24e46be4e

Tx prefix hash: bc9756c01b0d534f34a4364fda7b7fd01c1e640fdaad1a9acfe38e41e69965eb
Tx public key: 99b7c2d7fe579ec141e05c5f54a626e20052f4c82f69c09bbea7cb516153550c
Timestamp: 1750172605 Timestamp [UCT]: 2025-06-17 15:03:25 Age [y:d:h:m:s]: 00:205:16:50:17
Block: 1307028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144880 RingCT/type: yes/0
Extra: 0199b7c2d7fe579ec141e05c5f54a626e20052f4c82f69c09bbea7cb516153550c02110000000943846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf33edfaac8246b3056e373dbf2911c4d939c4b2f6688047dacfec2c70fe8224 0.600000000000 1794637 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": 1307038, "vin": [ { "gen": { "height": 1307028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf33edfaac8246b3056e373dbf2911c4d939c4b2f6688047dacfec2c70fe8224" } } ], "extra": [ 1, 153, 183, 194, 215, 254, 87, 158, 193, 65, 224, 92, 95, 84, 166, 38, 226, 0, 82, 244, 200, 47, 105, 192, 155, 190, 167, 203, 81, 97, 83, 85, 12, 2, 17, 0, 0, 0, 9, 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