Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa3d513521ba3cef3104ec22b5caceb25322f49bfd09de89b24ddcaa135a1220

Tx prefix hash: 96da8df4f1de3fa61df141dec52cd3eb157ad9ed580da484d2ec2b28fc4dbacd
Tx public key: c906b311315674f74dbf3a7a1a7d1f7efbfe5106990309039f7f825f84400006
Timestamp: 1746938436 Timestamp [UTC]: 2025-05-11 04:40:36 Age [y:d:h:m:s]: 00:278:22:32:28
Block: 1280350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196990 RingCT/type: yes/0
Extra: 01c906b311315674f74dbf3a7a1a7d1f7efbfe5106990309039f7f825f844000060211000000041f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d082fde82cc7b6f0d1132f6497f2d99f79c6a01543be1fe11cd0c58feb3ee165 0.000600000000 1767735 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": 1280360, "vin": [ { "gen": { "height": 1280350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d082fde82cc7b6f0d1132f6497f2d99f79c6a01543be1fe11cd0c58feb3ee165" } } ], "extra": [ 1, 201, 6, 179, 17, 49, 86, 116, 247, 77, 191, 58, 122, 26, 125, 31, 126, 251, 254, 81, 6, 153, 3, 9, 3, 159, 127, 130, 95, 132, 64, 0, 6, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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