Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73fe4ad9f59798fbe811862e40a02fcb83fb58c3e39e1b4f691864449d4cb4e3

Tx prefix hash: bc1ab4e9da76a005f2b29ac15c03e73c8f1473a738d45a12a5af7fa2c933d765
Tx public key: bf83508c20fee98621a9c4f4b98c00e5d6e0aab87c3f71c3f4d71ba4a0e60554
Timestamp: 1750059701 Timestamp [UCT]: 2025-06-16 07:41:41 Age [y:d:h:m:s]: 00:225:18:20:07
Block: 1306090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159060 RingCT/type: yes/0
Extra: 01bf83508c20fee98621a9c4f4b98c00e5d6e0aab87c3f71c3f4d71ba4a0e605540211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16bffdc6a597b000f425f1d88927ae4bdb2bf7f98cc9b8e274563e7764b99676 0.600000000000 1793693 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": 1306100, "vin": [ { "gen": { "height": 1306090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16bffdc6a597b000f425f1d88927ae4bdb2bf7f98cc9b8e274563e7764b99676" } } ], "extra": [ 1, 191, 131, 80, 140, 32, 254, 233, 134, 33, 169, 196, 244, 185, 140, 0, 229, 214, 224, 170, 184, 124, 63, 113, 195, 244, 215, 27, 164, 160, 230, 5, 84, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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