Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f78f75fab84fd866666e9dd89e7a3fd31df26e68019c010992bd41fccf7c17b

Tx prefix hash: 4d14e1f8013362a9f403279b1fe440405d2dc88e24090c8675c25b87e6060252
Tx public key: 08e1af41f0ecc92cc4eaa9ef53f248a15371b8f23b96c233b58a583ca08aef05
Timestamp: 1756320198 Timestamp [UCT]: 2025-08-27 18:43:18 Age [y:d:h:m:s]: 00:118:08:56:44
Block: 1355749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84566 RingCT/type: yes/0
Extra: 0108e1af41f0ecc92cc4eaa9ef53f248a15371b8f23b96c233b58a583ca08aef050211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b332047bc88a233f9e8a039d39bd98c559950861ee8941ae62e075f8a8beb3a4 0.600000000000 1843752 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": 1355759, "vin": [ { "gen": { "height": 1355749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b332047bc88a233f9e8a039d39bd98c559950861ee8941ae62e075f8a8beb3a4" } } ], "extra": [ 1, 8, 225, 175, 65, 240, 236, 201, 44, 196, 234, 169, 239, 83, 242, 72, 161, 83, 113, 184, 242, 59, 150, 194, 51, 181, 138, 88, 60, 160, 138, 239, 5, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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