Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b029e25341d9897f3fc8df115dc64be961b9f78e8bdabaee33d6011e26f08865

Tx prefix hash: 9e41b3c5f5f20d023f50a17d898f27ce073711a25c39bf75c54a45d01b1bc002
Tx public key: d522b3c597032b3df53ebff3cbfb0b343cf6672af42ca38bcd81e5d397e830d5
Timestamp: 1767112516 Timestamp [UTC]: 2025-12-30 16:35:16 Age [y:d:h:m:s]: 00:048:12:16:01
Block: 1445001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 34524 RingCT/type: yes/0
Extra: 01d522b3c597032b3df53ebff3cbfb0b343cf6672af42ca38bcd81e5d397e830d5020900000001df7c6e8400

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 80d3b25c364f3113de4e8ad0dccd57c1dd984ffc4dee15c9d577312e9f4792c4 0.000600000000 1933939 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": 1445011, "vin": [ { "gen": { "height": 1445001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80d3b25c364f3113de4e8ad0dccd57c1dd984ffc4dee15c9d577312e9f4792c4" } } ], "extra": [ 1, 213, 34, 179, 197, 151, 3, 43, 61, 245, 62, 191, 243, 203, 251, 11, 52, 60, 246, 103, 42, 244, 44, 163, 139, 205, 129, 229, 211, 151, 232, 48, 213, 2, 9, 0, 0, 0, 1, 223, 124, 110, 132, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369