Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4efd98e507dc6b19ede1096b032c95bb615c53023cfb74e8aa208e09e208aaf

Tx prefix hash: 859729559790f57d23f577f4270c0478072c57b9fe2f0b7c9422870e9a2a7e5c
Tx public key: 011f1808c52a540f1b109f76e6213524813f7923590c6b4cc4a411672fdaaaff
Timestamp: 1709062053 Timestamp [UCT]: 2024-02-27 19:27:33 Age [y:d:h:m:s]: 00:345:20:51:50
Block: 966887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247306 RingCT/type: yes/0
Extra: 01011f1808c52a540f1b109f76e6213524813f7923590c6b4cc4a411672fdaaaff02110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbcd38f8c7a424e3dae91933e83ebcac93c8a9a0878c9654f9d131e3c599c984 0.600000000000 1426658 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 dinasty-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": 966897, "vin": [ { "gen": { "height": 966887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbcd38f8c7a424e3dae91933e83ebcac93c8a9a0878c9654f9d131e3c599c984" } } ], "extra": [ 1, 1, 31, 24, 8, 197, 42, 84, 15, 27, 16, 159, 118, 230, 33, 53, 36, 129, 63, 121, 35, 89, 12, 107, 76, 196, 164, 17, 103, 47, 218, 170, 255, 2, 17, 0, 0, 0, 14, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8