Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc71f2805cf13bc7830e1e2c2107acc2db0a5907544e640bd99dd1f04cb0a1a2

Tx prefix hash: 17fbba56b85e865f375e710f0a878b1bc5b1b8c1dc1615a0a24b572d19cea15b
Tx public key: 1e0fb34185f5b039aee8e285aeb68a6336f3399f10dfef1bcc4a52aa74a26d3b
Timestamp: 1753981904 Timestamp [UTC]: 2025-07-31 17:11:44 Age [y:d:h:m:s]: 01:111:06:04:07
Block: 1337469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344759 RingCT/type: yes/0
Extra: 011e0fb34185f5b039aee8e285aeb68a6336f3399f10dfef1bcc4a52aa74a26d3b021100000010ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 50ba13ff6b8c41293b080abd8cf2e7ea09f7d25431444864e8788945f981812b 0.000600000000 1825274 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": 1337479, "vin": [ { "gen": { "height": 1337469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50ba13ff6b8c41293b080abd8cf2e7ea09f7d25431444864e8788945f981812b" } } ], "extra": [ 1, 30, 15, 179, 65, 133, 245, 176, 57, 174, 232, 226, 133, 174, 182, 138, 99, 54, 243, 57, 159, 16, 223, 239, 27, 204, 74, 82, 170, 116, 162, 109, 59, 2, 17, 0, 0, 0, 16, 173, 121, 72, 208, 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: