Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74666d0cd95e71d33e07f8a0aaffdc8e9c033b91c894c42cb68c5770bc88d5b7

Tx prefix hash: 53fea321c070a50add47e1213cb5e3d5524c4d2932b96344697dd881d7ee3528
Tx public key: e2d8855786227661f5b57147e8c47c33598f2c9ef188f1a89be1eb23a40632f3
Timestamp: 1772128617 Timestamp [UTC]: 2026-02-26 17:56:57 Age [y:d:h:m:s]: 00:267:03:08:50
Block: 1486357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196579 RingCT/type: yes/0
Extra: 01e2d8855786227661f5b57147e8c47c33598f2c9ef188f1a89be1eb23a40632f302110000000fe4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 485e8fdc6237419da0e8263e44208c95f93a1c02e48d7138967bf6cafc30cf57 0.000600000000 1975807 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": 1486367, "vin": [ { "gen": { "height": 1486357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "485e8fdc6237419da0e8263e44208c95f93a1c02e48d7138967bf6cafc30cf57" } } ], "extra": [ 1, 226, 216, 133, 87, 134, 34, 118, 97, 245, 181, 113, 71, 232, 196, 124, 51, 89, 143, 44, 158, 241, 136, 241, 168, 155, 225, 235, 35, 164, 6, 50, 243, 2, 17, 0, 0, 0, 15, 228, 245, 25, 63, 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) | monero version: