Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b7f37d426b49da364f641c75dd764ce1eaf5354810e97f9d6ce0a363196d392

Tx prefix hash: 2598582f04392916ac450435602995a19899129618cb34c2cb89ece720f4631c
Tx public key: 578e4cb6c7d89f3feb96a0e88329555bc20a91e31193ade97cef7886003116f2
Timestamp: 1770834963 Timestamp [UTC]: 2026-02-11 18:36:03 Age [y:d:h:m:s]: 00:003:20:04:08
Block: 1475682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 2716 RingCT/type: yes/0
Extra: 01578e4cb6c7d89f3feb96a0e88329555bc20a91e31193ade97cef7886003116f20208bb31966c6f5ca7a2

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 65d2ae3ec1c1ff2ddf670398c218d37f6f3e2dc6b18dd216f6dfb1d42923914e 0.000600000000 1964986 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": 1475692, "vin": [ { "gen": { "height": 1475682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65d2ae3ec1c1ff2ddf670398c218d37f6f3e2dc6b18dd216f6dfb1d42923914e" } } ], "extra": [ 1, 87, 142, 76, 182, 199, 216, 159, 63, 235, 150, 160, 232, 131, 41, 85, 91, 194, 10, 145, 227, 17, 147, 173, 233, 124, 239, 120, 134, 0, 49, 22, 242, 2, 8, 187, 49, 150, 108, 111, 92, 167, 162 ], "rct_signatures": { "type": 0 } }


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