Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5ba6135201e09dd0dbcf40b0405979d0cfb0b1ada15aaf7c218fd727676ba7b

Tx prefix hash: edcc97ab7329cad6a45d85a6b13e68bd50ba4a14407ab846409a011c276723aa
Tx public key: 461f38d7c22ab676cedf8f30fb3063c954f6ae2d22fbfe1bdf9e925a80050812
Timestamp: 1765770330 Timestamp [UCT]: 2025-12-15 03:45:30 Age [y:d:h:m:s]: 00:008:20:31:51
Block: 1433876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6339 RingCT/type: yes/0
Extra: 01461f38d7c22ab676cedf8f30fb3063c954f6ae2d22fbfe1bdf9e925a80050812021100000007d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 228eef2e9efa3acc2e1f2fcd95f8a9d06472450c2101e597dfa89733972d8411 0.600000000000 1922657 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": 1433886, "vin": [ { "gen": { "height": 1433876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "228eef2e9efa3acc2e1f2fcd95f8a9d06472450c2101e597dfa89733972d8411" } } ], "extra": [ 1, 70, 31, 56, 215, 194, 42, 182, 118, 206, 223, 143, 48, 251, 48, 99, 201, 84, 246, 174, 45, 34, 251, 254, 27, 223, 158, 146, 90, 128, 5, 8, 18, 2, 17, 0, 0, 0, 7, 214, 225, 157, 124, 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