Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84fc7a08ecd6b6ddc49a7f8503d469522ad50bf54d32ac3d191ab134e4ee78e6

Tx prefix hash: 468dd0510342e552e5c022f1ee4dcef43fcc75ffa49a669a3f004c9d02bb3eaa
Tx public key: fa79c75e8d8b63eafbe5107b865ff51ebbf4e2e8b536c3d849cc05c92c4bac3c
Timestamp: 1756230028 Timestamp [UCT]: 2025-08-26 17:40:28 Age [y:d:h:m:s]: 00:118:19:09:29
Block: 1355000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84867 RingCT/type: yes/0
Extra: 01fa79c75e8d8b63eafbe5107b865ff51ebbf4e2e8b536c3d849cc05c92c4bac3c0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fed995b23313a75bdd1a8e0b1bb1c9e1e7df599727ccd20f5461bc54dbe9dff 0.600000000000 1842995 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": 1355010, "vin": [ { "gen": { "height": 1355000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fed995b23313a75bdd1a8e0b1bb1c9e1e7df599727ccd20f5461bc54dbe9dff" } } ], "extra": [ 1, 250, 121, 199, 94, 141, 139, 99, 234, 251, 229, 16, 123, 134, 95, 245, 30, 187, 244, 226, 232, 181, 54, 195, 216, 73, 204, 5, 201, 44, 75, 172, 60, 2, 17, 0, 0, 0, 3, 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