Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e76cefabe0648a1131eaa46483d65872603a3542c75ca6fee7ddd97abeda342

Tx prefix hash: 001c591eff9d40e1dedd199291f5fd20971d0e17dfaad4ab743bf8ff0526714a
Tx public key: 1d64cf2ff506c13c49952d1f54e0dbd5c066db4496bb71796eb2a4ba34c1b783
Timestamp: 1717390349 Timestamp [UCT]: 2024-06-03 04:52:29 Age [y:d:h:m:s]: 00:342:06:01:29
Block: 1035928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244614 RingCT/type: yes/0
Extra: 011d64cf2ff506c13c49952d1f54e0dbd5c066db4496bb71796eb2a4ba34c1b783021100000001162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1fbaaeabd4c60daa4d3305099873d7bcc88655abccdf6ebfa1efa683b73f03f 0.600000000000 1504453 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": 1035938, "vin": [ { "gen": { "height": 1035928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1fbaaeabd4c60daa4d3305099873d7bcc88655abccdf6ebfa1efa683b73f03f" } } ], "extra": [ 1, 29, 100, 207, 47, 245, 6, 193, 60, 73, 149, 45, 31, 84, 224, 219, 213, 192, 102, 219, 68, 150, 187, 113, 121, 110, 178, 164, 186, 52, 193, 183, 131, 2, 17, 0, 0, 0, 1, 22, 38, 19, 170, 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