Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 735b7344ef197ed96fd49d693b28bf6c44b165bb9e101d68e0dfba0d44550c60

Tx prefix hash: 9092097d774c86624afa2a6594bad53137414a7149c690b429ed9f364287d108
Tx public key: 2685614fc85f4bc4fdaff2f4fd2db7ead6698fcd2fcb035c34af7193e82a5cd8
Timestamp: 1736098850 Timestamp [UCT]: 2025-01-05 17:40:50 Age [y:d:h:m:s]: 00:163:13:50:01
Block: 1190890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116609 RingCT/type: yes/0
Extra: 012685614fc85f4bc4fdaff2f4fd2db7ead6698fcd2fcb035c34af7193e82a5cd802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f9ca07b9c78af4f1783c1730b96e71ffcd6a48ee0a4ba49711c86acf9420c21 0.600000000000 1677413 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": 1190900, "vin": [ { "gen": { "height": 1190890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f9ca07b9c78af4f1783c1730b96e71ffcd6a48ee0a4ba49711c86acf9420c21" } } ], "extra": [ 1, 38, 133, 97, 79, 200, 95, 75, 196, 253, 175, 242, 244, 253, 45, 183, 234, 214, 105, 143, 205, 47, 203, 3, 92, 52, 175, 113, 147, 232, 42, 92, 216, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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