Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4165bcd1a15e7253faae8668a7719a1d62e65fa29a2a11682465d846990d0457

Tx prefix hash: 994b361162c8d9d412e7cf8f39adb8bf10011f7f8085b413ce5643f223f2b102
Tx public key: f5e8bcb2173504b97670e970eaba0c2d3763f0ebeb4393357930020e1c3eedbd
Timestamp: 1774761253 Timestamp [UTC]: 2026-03-29 05:14:13 Age [y:d:h:m:s]: 00:237:00:17:01
Block: 1508152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175045 RingCT/type: yes/0
Extra: 01f5e8bcb2173504b97670e970eaba0c2d3763f0ebeb4393357930020e1c3eedbd021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 785dbc21aeeb9d64998092d2f019e9a1f320cad69a56757cc69cecb09de34f98 0.000600000000 1997904 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": 1508162, "vin": [ { "gen": { "height": 1508152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "785dbc21aeeb9d64998092d2f019e9a1f320cad69a56757cc69cecb09de34f98" } } ], "extra": [ 1, 245, 232, 188, 178, 23, 53, 4, 185, 118, 112, 233, 112, 234, 186, 12, 45, 55, 99, 240, 235, 235, 67, 147, 53, 121, 48, 2, 14, 28, 62, 237, 189, 2, 17, 0, 0, 0, 2, 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: