Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd2ea7e270c5dd406c433eb0abd99bf5fbc050cde234b2c1cd91c3fe945084a2

Tx prefix hash: 5e4d7fbbd988a65038364d2ee61c6ef819d76e8c03a5a0124688a5cefa579efa
Tx public key: 9446dcf7c7e91bc28da67f5620a8353f5aa04fae93a08901188786a16598ff01
Timestamp: 1773135698 Timestamp [UTC]: 2026-03-10 09:41:38 Age [y:d:h:m:s]: 00:253:11:53:45
Block: 1494696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186707 RingCT/type: yes/0
Extra: 019446dcf7c7e91bc28da67f5620a8353f5aa04fae93a08901188786a16598ff01021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0f2c24e4aa73f271d134538f73f827b8737fba8fcd8ba7d32fcf6cc9017e5133 0.000600000000 1984268 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": 1494706, "vin": [ { "gen": { "height": 1494696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f2c24e4aa73f271d134538f73f827b8737fba8fcd8ba7d32fcf6cc9017e5133" } } ], "extra": [ 1, 148, 70, 220, 247, 199, 233, 27, 194, 141, 166, 127, 86, 32, 168, 53, 63, 90, 160, 79, 174, 147, 160, 137, 1, 24, 135, 134, 161, 101, 152, 255, 1, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: