Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d08a2d0c83858fca31dd761bca4ed3691a7bc163bc56bd1d1f83714f29d2337c

Tx prefix hash: e4fa459eee3b6acc030a23f58939c99df4c6d5708e967457b6ba2868c0b9eceb
Tx public key: 439bfb20dd6ffb861b07ed20fe119259885f8bca95e34421f7843a94d39e4314
Timestamp: 1759136156 Timestamp [UTC]: 2025-09-29 08:55:56 Age [y:d:h:m:s]: 01:048:23:29:52
Block: 1378891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301368 RingCT/type: yes/0
Extra: 01439bfb20dd6ffb861b07ed20fe119259885f8bca95e34421f7843a94d39e4314021100000002a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bdc7c6c7ce937aca5ab017052e539249f894bea846a9010a7c0c3ded4791298f 0.000600000000 1866988 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": 1378901, "vin": [ { "gen": { "height": 1378891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdc7c6c7ce937aca5ab017052e539249f894bea846a9010a7c0c3ded4791298f" } } ], "extra": [ 1, 67, 155, 251, 32, 221, 111, 251, 134, 27, 7, 237, 32, 254, 17, 146, 89, 136, 95, 139, 202, 149, 227, 68, 33, 247, 132, 58, 148, 211, 158, 67, 20, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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: