Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 787187975dd0a61bcdabc84cd49f3e56869897193574634bfa8c366d37ca3182

Tx prefix hash: 432029c0323230c718ebadf0caac580bdf3fa8b881429be9b77d06c315d4848c
Tx public key: 36582a343d7e43a3038d8e02f402662e1029d431c345bf3191df61fdc4cc5fcb
Timestamp: 1742970714 Timestamp [UTC]: 2025-03-26 06:31:54 Age [y:d:h:m:s]: 01:052:16:51:06
Block: 1247499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288741 RingCT/type: yes/0
Extra: 0136582a343d7e43a3038d8e02f402662e1029d431c345bf3191df61fdc4cc5fcb021100000003165b77a1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f96977443d448e278226fb753922d34d9a970219d0a663e59e1efef4aa808d57 0.000600000000 1734516 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": 1247509, "vin": [ { "gen": { "height": 1247499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f96977443d448e278226fb753922d34d9a970219d0a663e59e1efef4aa808d57" } } ], "extra": [ 1, 54, 88, 42, 52, 61, 126, 67, 163, 3, 141, 142, 2, 244, 2, 102, 46, 16, 41, 212, 49, 195, 69, 191, 49, 145, 223, 97, 253, 196, 204, 95, 203, 2, 17, 0, 0, 0, 3, 22, 91, 119, 161, 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: