Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53924eee81ce3f31f3bfe9ab1d27ec9fe8cb63c0f86c8652f056e3ce5feb191e

Tx prefix hash: 07d92045086dbcc3f095aea3f48e0a572fef67d6730df630f3435fc90bbabcb1
Tx public key: 593521b39279e4b82560614ddfc6c96e858f3ccb8a1f489004147ff46c787818
Timestamp: 1740470538 Timestamp [UCT]: 2025-02-25 08:02:18 Age [y:d:h:m:s]: 00:317:00:52:11
Block: 1226793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224432 RingCT/type: yes/0
Extra: 01593521b39279e4b82560614ddfc6c96e858f3ccb8a1f489004147ff46c7878180211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a50f446f59bb78e6b7efd9ebf809250a834d24a5e23f5a4d975472c7f5e55e5 0.600000000000 1713666 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": 1226803, "vin": [ { "gen": { "height": 1226793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a50f446f59bb78e6b7efd9ebf809250a834d24a5e23f5a4d975472c7f5e55e5" } } ], "extra": [ 1, 89, 53, 33, 179, 146, 121, 228, 184, 37, 96, 97, 77, 223, 198, 201, 110, 133, 143, 60, 203, 138, 31, 72, 144, 4, 20, 127, 244, 108, 120, 120, 24, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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