Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5a3f96cf5b6948285d448803b7eff5ee08fd07df3c07c99c01c95c2fb2dc30b

Tx prefix hash: 20597561efff03e5e58ccd1485037dc4db9c656eca09dde51911c03507857ce3
Tx public key: e604c482137d14779a1e652b4162d3ae70c82ff1b352fb0c0cd549797b8c9b06
Timestamp: 1704505559 Timestamp [UCT]: 2024-01-06 01:45:59 Age [y:d:h:m:s]: 01:091:18:20:15
Block: 929071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326697 RingCT/type: yes/0
Extra: 01e604c482137d14779a1e652b4162d3ae70c82ff1b352fb0c0cd549797b8c9b0602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5005ce3f622042d4f145f4aef5771a170b676164d95bdfe3a1804e7961a5f48a 0.600000000000 1386939 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": 929081, "vin": [ { "gen": { "height": 929071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5005ce3f622042d4f145f4aef5771a170b676164d95bdfe3a1804e7961a5f48a" } } ], "extra": [ 1, 230, 4, 196, 130, 19, 125, 20, 119, 154, 30, 101, 43, 65, 98, 211, 174, 112, 200, 47, 241, 179, 82, 251, 12, 12, 213, 73, 121, 123, 140, 155, 6, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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