Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c394f4a609c062fb8d42dd1b255c39634afc414b42fa5f13cf966f02beebea6c

Tx prefix hash: 338f8ac242ca56e6af7d4905aff507e988ff72ef747dd883e6ade73a67148bbd
Tx public key: d1b377229a75e5312c8239c8854e35d44d77088f09a32ac08a7cf0603e71ae3e
Timestamp: 1761348712 Timestamp [UTC]: 2025-10-24 23:31:52 Age [y:d:h:m:s]: 01:028:04:27:30
Block: 1397253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286241 RingCT/type: yes/0
Extra: 01d1b377229a75e5312c8239c8854e35d44d77088f09a32ac08a7cf0603e71ae3e021100000001e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5d2c2ca7d5b02be483fe2f0e4b22080755caea634bb991dad3e2fce369052065 0.000600000000 1885544 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": 1397263, "vin": [ { "gen": { "height": 1397253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d2c2ca7d5b02be483fe2f0e4b22080755caea634bb991dad3e2fce369052065" } } ], "extra": [ 1, 209, 179, 119, 34, 154, 117, 229, 49, 44, 130, 57, 200, 133, 78, 53, 212, 77, 119, 8, 143, 9, 163, 42, 192, 138, 124, 240, 96, 62, 113, 174, 62, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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: