Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f42553b7ff5ebb2ac48df026ad450d6a2bef95d7da33d548e17ec71c8de2bb54

Tx prefix hash: 6c0bb17262a713a552ff55230c89da7471c3d56c2e8e92941668d22bf948ad54
Tx public key: 584b0f02861fdacc3439fb2b46fb023cf5099cd54eb1632d86c2c25707489c55
Timestamp: 1768419502 Timestamp [UTC]: 2026-01-14 19:38:22 Age [y:d:h:m:s]: 00:032:02:27:04
Block: 1455689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22928 RingCT/type: yes/0
Extra: 01584b0f02861fdacc3439fb2b46fb023cf5099cd54eb1632d86c2c25707489c55021100000009215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cf59d650ac546a3fc34ef64596d507a25fc90c9aa10d7a373f31ff9b3458d8e7 0.000600000000 1944787 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 dinastycoin-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": 1455699, "vin": [ { "gen": { "height": 1455689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf59d650ac546a3fc34ef64596d507a25fc90c9aa10d7a373f31ff9b3458d8e7" } } ], "extra": [ 1, 88, 75, 15, 2, 134, 31, 218, 204, 52, 57, 251, 43, 70, 251, 2, 60, 245, 9, 156, 213, 78, 177, 99, 45, 134, 194, 194, 87, 7, 72, 156, 85, 2, 17, 0, 0, 0, 9, 33, 91, 191, 137, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369