Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 326bfabe041499dd87a534de32603b1dd5bfaa50ccf6ec7df4e08052e55a50cb

Tx prefix hash: 7f27d0624dbf044524a4999964b5a6f6be6d3414a8929783efb4e550007f3584
Tx public key: fc65d249de392cd1a2ebd62ad16b42c3c9e6e07200ae1894670f23763ff67f86
Timestamp: 1756367910 Timestamp [UTC]: 2025-08-28 07:58:30 Age [y:d:h:m:s]: 01:084:04:40:25
Block: 1356142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326545 RingCT/type: yes/0
Extra: 01fc65d249de392cd1a2ebd62ad16b42c3c9e6e07200ae1894670f23763ff67f860211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 41146366e2c621bf1122c8e109c44d62546cd6b312f3fa068579245ff837d12f 0.000600000000 1844147 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": 1356152, "vin": [ { "gen": { "height": 1356142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41146366e2c621bf1122c8e109c44d62546cd6b312f3fa068579245ff837d12f" } } ], "extra": [ 1, 252, 101, 210, 73, 222, 57, 44, 209, 162, 235, 214, 42, 209, 107, 66, 195, 201, 230, 224, 114, 0, 174, 24, 148, 103, 15, 35, 118, 63, 246, 127, 134, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: