Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12e4ac6ca64da4348ca03110903d7bbd72c4e6607297876caf27814b1de3fae2

Tx prefix hash: 66925a602dbbaf230e68682133b9564d2ac9bc4b937fbca7d8387f430b1c73d4
Tx public key: ea911703726a9578ff4335710b45a88ba2381b7555019fdaf2d6aea3c4e1793b
Timestamp: 1575137665 Timestamp [UTC]: 2019-11-30 18:14:25 Age [y:d:h:m:s]: 06:080:01:56:43
Block: 21030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0967 kB
Tx version: 2 No of confirmations: 1458244 RingCT/type: yes/0
Extra: 01ea911703726a9578ff4335710b45a88ba2381b7555019fdaf2d6aea3c4e1793b020d393030310002000000024c7e9f

1 output(s) for total of 0.522780952085 xmr

stealth address amount amount idx tag
00: fc61e7816bc3ba2595e6e5d1c9d1a8ff2e1712a9d28f9298aa4c1acdcb41cc4f 0.522780952085 33527 of 0 -

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": 21040, "vin": [ { "gen": { "height": 21030 } } ], "vout": [ { "amount": 522780952085, "target": { "key": "fc61e7816bc3ba2595e6e5d1c9d1a8ff2e1712a9d28f9298aa4c1acdcb41cc4f" } } ], "extra": [ 1, 234, 145, 23, 3, 114, 106, 149, 120, 255, 67, 53, 113, 11, 69, 168, 139, 162, 56, 27, 117, 85, 1, 159, 218, 242, 214, 174, 163, 196, 225, 121, 59, 2, 13, 57, 48, 48, 49, 0, 2, 0, 0, 0, 2, 76, 126, 159 ], "rct_signatures": { "type": 0 } }


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