Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ccd9ed92fcdb767f7ea116d9e5cfb2b593995309e0103601afb01b90377741d

Tx prefix hash: 126bbf38b6ed8802edc902061f5f6bb59a428452f349f115d9c471a3b5020992
Tx public key: 429736827f37a66b13451605b410cffc19040e84dce815fb996b10b1ac9e88c5
Timestamp: 1765512225 Timestamp [UTC]: 2025-12-12 04:03:45 Age [y:d:h:m:s]: 00:340:12:46:28
Block: 1431741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248765 RingCT/type: yes/0
Extra: 01429736827f37a66b13451605b410cffc19040e84dce815fb996b10b1ac9e88c5021100000013d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 40cf49ec5f02932f4a6e160e692e3495d58e2d5dfc6986bde74291daf9b236c5 0.000600000000 1920514 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": 1431751, "vin": [ { "gen": { "height": 1431741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40cf49ec5f02932f4a6e160e692e3495d58e2d5dfc6986bde74291daf9b236c5" } } ], "extra": [ 1, 66, 151, 54, 130, 127, 55, 166, 107, 19, 69, 22, 5, 180, 16, 207, 252, 25, 4, 14, 132, 220, 232, 21, 251, 153, 107, 16, 177, 172, 158, 136, 197, 2, 17, 0, 0, 0, 19, 214, 225, 157, 124, 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: