Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebe58e21d60b60a961870e63afd675d938a22434b6ee792ecd0c14e8c2a708e6

Tx prefix hash: aa9ddd15c6e88247c8968d32d4746a1534543864068f450063e42e746f11d0ef
Tx public key: 825a946c8813801a156a46c22af7d45a40ee39b710d054e39160ce4269ec1f65
Timestamp: 1758416271 Timestamp [UTC]: 2025-09-21 00:57:51 Age [y:d:h:m:s]: 01:061:13:35:04
Block: 1372936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310535 RingCT/type: yes/0
Extra: 01825a946c8813801a156a46c22af7d45a40ee39b710d054e39160ce4269ec1f65021100000002b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f72414ed25245bb22e1d435af801977eecc015e1b576398372839ef097f05a60 0.000600000000 1861021 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": 1372946, "vin": [ { "gen": { "height": 1372936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f72414ed25245bb22e1d435af801977eecc015e1b576398372839ef097f05a60" } } ], "extra": [ 1, 130, 90, 148, 108, 136, 19, 128, 26, 21, 106, 70, 194, 42, 247, 212, 90, 64, 238, 57, 183, 16, 208, 84, 227, 145, 96, 206, 66, 105, 236, 31, 101, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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: