Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2c19fd5443a2756ab40a984f90f53c787cd93928286fb51792cb0ffd9a31612

Tx prefix hash: 0680f7eec338adda2e1a3db27587ab016f092e74b05210e6f303f2093ab7501f
Tx public key: 6ff51385426069dec54a84c1b513f1cc58e62813383cee9dc8504acf0ff33cd0
Timestamp: 1742743965 Timestamp [UTC]: 2025-03-23 15:32:45 Age [y:d:h:m:s]: 01:056:17:37:55
Block: 1245642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292511 RingCT/type: yes/0
Extra: 016ff51385426069dec54a84c1b513f1cc58e62813383cee9dc8504acf0ff33cd0021100000001c6740958000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 171545acba4662df258e2e456a02924796830e6e4d7ae4cfaf14ce9900d97430 0.000600000000 1732633 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": 1245652, "vin": [ { "gen": { "height": 1245642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "171545acba4662df258e2e456a02924796830e6e4d7ae4cfaf14ce9900d97430" } } ], "extra": [ 1, 111, 245, 19, 133, 66, 96, 105, 222, 197, 74, 132, 193, 181, 19, 241, 204, 88, 230, 40, 19, 56, 60, 238, 157, 200, 80, 74, 207, 15, 243, 60, 208, 2, 17, 0, 0, 0, 1, 198, 116, 9, 88, 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: