Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffaa9ff4c6b1ba51e9ad12d38d5cc5b808d8f6ad3f8c645fc3039744fc37f3ad

Tx prefix hash: 954bcfc89da09be94d17b12c0bb24c52431c054ea661c30aadbf49f9374a82a4
Tx public key: 8240c031b89466122f2aced0c4bbeaa5eb6b1389f5899a2fc1008ea01b474bd8
Timestamp: 1761672188 Timestamp [UTC]: 2025-10-28 17:23:08 Age [y:d:h:m:s]: 00:197:20:53:02
Block: 1399926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133737 RingCT/type: yes/0
Extra: 018240c031b89466122f2aced0c4bbeaa5eb6b1389f5899a2fc1008ea01b474bd802110000000225a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 08d2b9ac9c64221551e2cc55f67b9f7d446089ab166b3a34124c71bdb5a4f2b4 0.000600000000 1888233 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": 1399936, "vin": [ { "gen": { "height": 1399926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08d2b9ac9c64221551e2cc55f67b9f7d446089ab166b3a34124c71bdb5a4f2b4" } } ], "extra": [ 1, 130, 64, 192, 49, 184, 148, 102, 18, 47, 42, 206, 208, 196, 187, 234, 165, 235, 107, 19, 137, 245, 137, 154, 47, 193, 0, 142, 160, 27, 71, 75, 216, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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: