Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a4e3638ecc64d3bc6560ee37db1e23d735fef77a0fdcb69a6c3edcc11eb84f4

Tx prefix hash: 53622294a7d0bd8828f6ef70602b9c95d1b84279dc03e2b6247c1dad3b8cee53
Tx public key: dbc33e886fa19b70779f3f03afbc018423a0cd981e0472bd17ff414152db14d1
Timestamp: 1735779449 Timestamp [UTC]: 2025-01-02 00:57:29 Age [y:d:h:m:s]: 01:318:02:56:04
Block: 1188240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491140 RingCT/type: yes/0
Extra: 01dbc33e886fa19b70779f3f03afbc018423a0cd981e0472bd17ff414152db14d1021100000006007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 345c1dbbd086f7c6d29607d60e064439b4b8dd8da68e917d64e24b921ad81f75 0.000600000000 1674741 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": 1188250, "vin": [ { "gen": { "height": 1188240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "345c1dbbd086f7c6d29607d60e064439b4b8dd8da68e917d64e24b921ad81f75" } } ], "extra": [ 1, 219, 195, 62, 136, 111, 161, 155, 112, 119, 159, 63, 3, 175, 188, 1, 132, 35, 160, 205, 152, 30, 4, 114, 189, 23, 255, 65, 65, 82, 219, 20, 209, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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: