Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30c43f2dcf0d5f5f24792956a2deeca74c175d1f5494cedd0c3f4a04a49c1bf8

Tx prefix hash: 930c614f6acd84f05b7c4efd4a1b6b880e4429f5689f7227bc576dc5b5517121
Tx public key: e8c1a9f58562b0851aa21f3343931c9008ea4c3c61fef42116440f0114115065
Timestamp: 1766855248 Timestamp [UTC]: 2025-12-27 17:07:28 Age [y:d:h:m:s]: 00:068:18:30:48
Block: 1442870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49031 RingCT/type: yes/0
Extra: 01e8c1a9f58562b0851aa21f3343931c9008ea4c3c61fef42116440f011411506502110000000570609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e77595b89f69eea7e23d3348a1b29cc9515d160e44fa2e3f2c4f0d9b98e1e26c 0.000600000000 1931771 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": 1442880, "vin": [ { "gen": { "height": 1442870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e77595b89f69eea7e23d3348a1b29cc9515d160e44fa2e3f2c4f0d9b98e1e26c" } } ], "extra": [ 1, 232, 193, 169, 245, 133, 98, 176, 133, 26, 162, 31, 51, 67, 147, 28, 144, 8, 234, 76, 60, 97, 254, 244, 33, 22, 68, 15, 1, 20, 17, 80, 101, 2, 17, 0, 0, 0, 5, 112, 96, 157, 3, 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) | dinastycoin version: tesla-369